Agility CMS

Get a list of available Agility instances.

get_available_instances

Get a list of Agility components (page modules) for a particular instance. Includes Agility's built-in components (e.g. RichTextArea) by default so their model IDs are discoverable for embedding in pages; set includeBuiltIn:false to list only instance-defined components. A component with a thumbnail lists its URL: a picture of what the component looks like on a page.

get_component_models

Gets the list of Agility containers (content lists and single items) for a particular instance. The full container list is retrieved (paged) from Agility, then the optional search filter and take/skip pagination are applied to the results. By default returns the first 50 containers.

get_containers

Retrieve a list of content items from an Agility CMS container. Returns items with standard properties (contentID, versionID, state, dates) and a dynamic 'fields' object based on the container schema. Field names are CASE-INSENSITIVE for reads (e.g., 'Title' is the same as 'title'). By default, all configured fields are returned. You can optionally specify a list of field names to return only specific fields. **IMPORTANT NOTES:** - **Staging items:** Newly created items with state=1 (staging) may not appear in list results. Use `get_content_item` with the specific contentID to verify creation. - **Text field filters:** The `filter` parameter may return inconsistent results for text field searches. For small containers, consider fetching all items and filtering client-side. - **Empty fields:** Items may appear with empty fields if: (1) content was saved to the wrong locale, (2) the container is a nested/inline content list (e.g., page module child lists). If you get items with empty fields, first verify the locale matches `get_locales`, then try `get_content_item` with the individual contentID to get full field data.

get_content_items

Get a list of Agility content models for a particular instance.

get_content_models

Get a list of locales for an Agility instance.

get_locales

List media assets in an Agility CMS instance's media library, paged. Use this to find existing assets (e.g. to detect duplicates before uploading, or to find a mediaID to delete). Returns mediaID, fileName, URL, content type, size, and folder for each asset, plus the total count.

list_media

Get a list of Agility page models (templates) for a particular instance and locale. Pass includeModuleZones: true to also return each model's content zones — the zone reference names you need as the `zones` keys when adding components via save_page.

get_page_models

Retrieve a list of all sitemaps for an Agility CMS instance. Returns only the channel IDs and names for quick reference. Use this before calling get_sitemap to see available sitemaps.

get_sitemaps

Move one or more content items through Agility's approval workflow. **Operations:** - `approve` — approve an item awaiting approval - `decline` — decline an item awaiting approval - `request-approval` — submit an item for approval To take content live/offline, use `publish_content` / `unpublish_content`. Runs with your Agility account's permissions (enforced by the Management API).

manage_content_workflow

Move one or more pages through Agility's approval workflow. **Operations:** - `approve` — approve a page awaiting approval - `decline` — decline a page awaiting approval - `request-approval` — submit a page for approval To take a page live/offline, use `publish_page` / `unpublish_page`. Runs with your Agility account's permissions (enforced by the Management API).

manage_page_workflow

Publish one or more content items in Agility CMS — take them live (Staging/Approved → Published). This is how you take saved content live — `save_content_items` always saves to the instance's default state (typically Staging) and does NOT publish. Runs with your Agility account's permissions (enforced by the Management API) — if you lack publish rights, the API denies it. Reversible via `unpublish_content`.

publish_content

Publish one or more pages in Agility CMS — take them live. This is how you take a saved page live — `save_page` saves to the instance's default state (typically Staging) and does NOT publish. Runs with your Agility account's permissions (enforced by the Management API). Reversible via `unpublish_page`.

publish_page

Reorder the modules/components within a specific zone of a page. This is a lightweight alternative to save_page when you only need to change the order of existing modules. Provide the pageID, zoneName, and an array of contentIDs in the desired order.

reorder_page_modules

Save a new or existing Agility component model. Always check the listing of current component models before creating a new one. The `model` parameter is EXACTLY the same shape as `save_content_model`'s — see that tool's inputSchema for the full field specification (all field types, including the various Linked Content types); it is validated identically here on save. The two tools are NOT interchangeable on an existing model: saving a content model through this tool converts it. Include all appropriate properties on all fields as undefined properties will be interpreted as empty or null values.

save_component_model

Save a new or existing Agility container. Always check the listing of current containers before creating a new one.

save_container

Save or update one or more content items in Agility CMS. **BEFORE SAVING:** Retrieve the container's content model (get_content_model_details) to understand field types and requirements. **FOR NEW ITEMS (contentID = -1):** - Provide referenceName and fields object with content data - definitionName is auto-inferred from referenceName if not provided - For NEW attachments: (1) Call initialize_media_upload to get an uploadUrl, (2) POST file to that URL, (3) Use the returned asset URL in the attachment field **FOR UPDATES (contentID > 0):** - Include ALL fields, not just changed fields — omitted fields are wiped - Include properties.versionID with the current version ID - Recommended: First call get_content_item to retrieve current field values and versionID - For EXISTING attachments, use the current URL directly **KEY REQUIREMENTS:** - Field names are case-insensitive (e.g., 'Title', 'title', and 'TITLE' all work) - Link fields use {href, text, target} format. Target is auto-defaulted if omitted. Non-absolute hrefs must use the "~/" site-root prefix (e.g. "~/about-us", NOT "/about-us") — leading-slash or bare relative hrefs are auto-corrected to the "~/" form and reported. - LinkedContent fields (SearchListBox, Dropdown) require companion _TextField and _ValueField — check get_content_model_details for the exact field names - For "User Selectable" linked-content fields, the field value is the linked container's reference name. Case is normalized automatically to the canonical case from get_containers (the editor matches case-sensitively). - Container and locale are validated before saving — invalid values return an immediate error with available options - **`seo` only applies to items in a dynamic page list.** Item-level SEO attaches to the page each item generates, which requires `isDynamicPageList` on the container. Elsewhere Agility ignores it, so it is dropped and reported while the rest of the item saves normally — omit `seo` for ordinary containers. - **`geo` (GEO/AEO): same dynamic-page-list rule.** Three-state: omit = keep stored, null = clear (`geo: null` clears all), value = replace. - **Saving never changes workflow state:** items are saved to the instance's default workflow state (typically Staging). To take content live use `publish_content` (or `unpublish_content`); to move it through approval use `manage_content_workflow` after saving. Returns per-item results including contentID, the containerID, and an editUrl for each saved item. On partial failure, returns both successful IDs and per-item error details from the batch.

save_content_items

Save a new or existing Agility content model. Always check the listing of current content models before creating a new one. Take note of the different field types available, especially the various Linked Content types. Include all appropriate properties on all fields as undefined properties will be interpreted as empty or null values. NOTE: the `model` shape documented here is also exactly what `save_component_model` accepts — but they are NOT interchangeable on an existing model: saving a component through this tool converts it and orphans its nested content.

save_content_model

Save a new page or update an existing page in Agility CMS. This tool supports 4 page types: 1. **static** - Regular content pages with zones and components 2. **dynamic** - Pages generated from a content list with dynamic formulas, as well as zones and components 3. **folder** - Organizational containers with no content 4. **link** - Redirect pages that point to other URLs **PREREQUISITES - Before creating a page, you MUST gather:** 1. **Locale** - Use `get_locales` to get valid locale codes for the instance 2. **Sitemap/Channel** - Use `get_sitemaps` to list available sitemaps and get their IDs 3. **Page Model** - Use `get_page_models` to list available page models and their names. The modelName field is REQUIRED for static and dynamic pages. 4. **Parent Page** (if applicable) - Use `get_sitemap` to find the parent page ID by name/path. Do NOT guess parentPageID. 5. **Component Models** (for static/dynamic pages with zones) - Use `get_component_models` to list available components, then `get_component_model_details` to get field definitions for each component you want to add. **CRITICAL - Zone names:** the keys of the `zones` object MUST exactly match the zone reference names defined by the page model (they are case-sensitive). Get them from `get_page_models` (with `includeModuleZones`) — do NOT guess. A common zone is `MainContentZone`, but it varies by template. Components placed in a zone the template doesn't define are silently discarded by the API; this tool now rejects unknown zone names up front. **CRITICAL - Adding Components to Pages (static/dynamic pages):** When adding components to page zones, you can create the content items DIRECTLY in the page JSON - DO NOT call save_content_items first! For NEW components, embed the full content item in the zones array (do NOT include contentID), and be sure to include the correct componentModelID for the component model. Replace the zone key below with a real zone name from get_page_models: ```json zones: { "MainContentZone": [{ component: "RichTextArea", item: { fields: { textblob: "<p>Your content here</p>" }, properties: { componentModelID: 123 } } }] } ``` For EXISTING components (already created separately), just reference by ID: ```json item: { contentId: 123 } ``` The save_page tool will create both the page AND all embedded content items in a single operation. **Link fields in component items:** use {href, text, target}. Non-absolute hrefs must use the "~/" site-root prefix (e.g. "~/about-us", NOT "/about-us") — leading-slash or bare relative hrefs are auto-corrected on save. **Visibility/SEO:** `visible` sets menu/sitemap visibility; `seo.menuVisible`/`sitemapVisible` apply only to keys `visible` leaves unset (an update keeps stored values for the rest). Omit `seo`, `scripts` or a key in them to keep it; "" clears. **SEO/GEO:** `seo.title`/`canonicalUrl`/`robots`/`ogImage` and `geo` are three-state: omit = keep stored, null = clear (`geo: null` clears all of it), value = replace. **IMPORTANT LIMITATIONS:** - **Reordering:** `save_page` does NOT reorder existing components. To change module order, use `reorder_page_modules` after saving. - **Content copies:** When referencing an existing contentId on a NEW page, the API creates a COPY of that content with a new ID. It does not reference the original. Plan accordingly. - **Locale:** Validated before saving. Use `get_locales` to confirm the correct locale — saving to the wrong locale creates orphaned content.

save_page

Create a new or update an existing Agility page model (page template). A page model defines the content zones where editors can place components/modules. Check existing models with get_page_models before creating one. To update a model, pass its id (pageModelID) and its COMPLETE zone list: any zone left out is deleted, and pages lose the components placed in it until re-added by referenceName. Read current zones first via get_page_models (includeModuleZones: true).

save_page_model

Full-text search of one instance: content items, components, pages, assets, models and containers. Use it to find things by name, text or ID instead of paging through lists. - Words match as prefixes ("newsl" finds "newsletter") and every word must match; "quoted text" is an exact phrase; a number also matches content, page, asset and model IDs exactly. - relaxed=true means nothing matched every word, so hits match ANY word. - facets count every kind; narrow with kinds. containers/models/state limit to content kinds. - Act on hits with their IDs: get_content_item (contentID), get_page (pageID), get_content_items (containerReferenceName), get_content_model_details (modelID).

search_instance

Unpublish one or more content items in Agility CMS — take live items offline (Published → Unpublished). Removes the item(s) from the live site, so clients may prompt before running this. Runs with your Agility account's permissions (enforced by the Management API). Reversible via `publish_content`.

unpublish_content

Unpublish one or more pages in Agility CMS — take live pages offline. Removes the page(s) from the live site, so clients may prompt before running this. Runs with your Agility account's permissions (enforced by the Management API). Reversible via `publish_page`.

unpublish_page