MCP Tool CatalogBetaThis catalog summarizes every tool exposed by the Agility MCP server, including the input parameters, response shape, and practical usage notes. All tools require an authenticated request with a valid OAuth token.
Start here to understand what instances, locales, and containers are available before you read or write content.
get_available_instancesLists every Agility CMS instance the authenticated user can access.
Groups instances by organization and provides quick links so you can pick the right environment before working with content or models.
No parameters required. The tool reads from the authenticated account context.
Array of instances with `guid`, `name`, `org`, and `appUrl` grouped by organization for easy browsing.
get_localesRetrieves all locales configured for an instance.
Use this first when planning localized operations so you can request and save content in the correct locale code.
The Agility instance to inspect.
Array of locale records containing locale name and locale code.
get_containersLists content containers (lists and singletons) for an instance.
Provides containers grouped by category with search and pagination. Returns display name, reference name, content definition name, and model ID for each container.
The target Agility instance.
Filter containers by display name, reference name, or category (case-insensitive).
Maximum containers to return (default: 50).
Number of containers to skip for pagination (default: 0).
Array of container definitions including display name, ID, reference name, content definition name, and category. Includes totalCount, filteredCount, skip, and take metadata.
Inspect and manage the underlying content and component schemas that power your Agility CMS implementation.
get_content_modelsLists all content models for an instance.
Helpful when discovering schema names before building prompts or generating content payloads.
Instance that owns the content models.
Array of content models with identifiers and display information.
get_component_modelsLists all component models for an instance.
Use this when you need to inspect reusable components that can be embedded into other content types.
Instance that owns the component models.
Array of component models with display names, references, and IDs.
get_page_modelsLists all page models for an instance and locale.
Retrieves available page models that define the structure and layout of pages. Use this to discover which page models can be assigned when creating or updating pages.
Instance that owns the page models.
Locale code such as `en-us`.
Whether to include module zone details (default: false).
Optional search filter for page models.
Array of page models with display names, IDs, and configuration details.
get_content_model_detailsReturns the full definition for a specific content model.
Accepts either the model ID or reference name (one or the other) and returns field definitions so you can craft valid payloads.
Instance that contains the content model.
Numeric model ID. Provide this or `referenceName`, but not both.
Model reference name. Provide this or `modelID`, but not both.
Content model metadata including display information, description, and an array of fields with type information.
get_component_model_detailsReturns the full definition for a specific component model.
Accepts either the model ID or reference name (one or the other) and returns the component's fields and configuration.
Instance that contains the component model.
Numeric component model ID. Provide this or `referenceName`, but not both.
Component reference name. Provide this or `modelID`, but not both.
Component model metadata including display information, description, and detailed field configuration.
save_content_modelCreates or updates a content model using the enhanced model schema.
Use after generating a model definition to push schema changes into Agility CMS. Accepts complex field configurations via `EnhancedModelSchema`.
Instance where the model should be saved.
Model definition including fields, IDs, reference name, and metadata.
Saved content model including updated IDs, reference name, and persisted field configuration.
save_component_modelCreates or updates a component model using the enhanced model schema.
Pushes component schema updates, supporting the same field configuration helpers used for content models.
Instance where the component model should be saved.
Component model definition including fields and identifying information.
Saved component model with IDs, reference name, and resolved field configuration.
Fetch content in bulk or read a single item to inform prompts, transformations, or audits.
get_content_itemsRetrieves a paged list of content items for a container.
Supports paging, filtering, field selection, and sorting to help explore current content.
Instance that owns the content.
Container reference name to query.
Locale code such as `en-us`.
Maximum number of items to return (default 50).
Number of items to skip for paging (default 0).
Search query string applied server-side.
Field name to sort by (ascending by default).
Optional list of field names to include; system fields are always returned.
Structured list containing items with system properties and a dynamic `fields` object plus pagination counts.
get_content_itemRetrieves one or more content items by ID.
Supports single and batch retrieval (up to 50 items). Batch requests are fetched concurrently in chunks of 10 with partial results on individual failures.
Instance that owns the item(s).
Single content item ID (use this OR contentIDs, not both).
Array of content item IDs for batch retrieval (max 50). Use this OR contentID.
Locale code such as `en-us`.
Single item: full content item with properties, fields, SEO, and scripts. Batch: items array with optional errors array for failed retrievals.
get_sitemapsLists all digital channels (sitemaps) for an instance.
Returns a lightweight list of channel IDs and names only. Use this first to see available channels before retrieving full sitemap structures with get_sitemap.
Instance that owns the channels.
Locale code such as `en-us`.
Array of channel summaries with `digitalChannelID` and `name` properties only.
get_sitemapRetrieves a specific sitemap with filtering options.
Returns the page hierarchy for a channel. Supports maxDepth, pathPrefix, and flat mode to reduce response size for large sitemaps.
Instance that owns the sitemap.
Locale code such as `en-us`.
Channel/sitemap name (case-insensitive). Omit to get the default sitemap.
Sitemap ID to retrieve. Takes priority over sitemapName.
Maximum depth of pages to return (e.g., 2 = top-level + children).
Filter to pages whose URL starts with this prefix (e.g., '/blog'). Case-insensitive.
If true, returns a flat list of {pageID, pageName, path, parentPageID} instead of nested tree.
Nested page tree or flat page list with page IDs, URLs, types, and dynamic content references.
get_pageRetrieves a single page by ID.
Returns complete page details including zones, components, SEO settings, and page configuration. Useful for inspecting existing pages before modification.
Instance that owns the page.
Page ID to retrieve.
Locale code such as `en-us`.
Complete page object with all zones, component references, SEO configuration, and page metadata.
Create or update content structures and entries once your prompts have prepared valid payloads.
save_content_itemsCreates or updates one or more content items with pre-save validation.
Validates locale, container existence, and field types before saving. Auto-infers definitionName from referenceName. Returns per-item results on partial success so agents know exactly which items saved and which failed.
Instance that owns the content.
Locale code such as `en-us`. Validated against available locales.
Array of content items including `contentID` (-1 for new), `referenceName`, `fields`, and optional `properties`.
An `items` array in the same order as the input. Each entry has `saved: true` with a `contentID`, or `saved: false` with an `error` message. Also includes `savedCount` and `failedCount` totals. If every item fails, throws an error with per-item details instead.
save_containerCreates or updates a container definition.
Uses the enhanced container schema to manage list or details containers, including linked fields and presentation settings.
Instance where the container should be saved.
Container definition supporting both legacy and enhanced field formats.
Saved container metadata including IDs, reference names, and display information.
Create, update, and manage pages and their module layouts within your site's sitemap structure.
save_pageCreates or updates a page in Agility CMS.
Supports creating and updating static, dynamic, folder, and link pages. Validates locale before saving.
Instance where the page should be saved.
Locale code such as `en-us`.
Page object with pageType ('static', 'dynamic', 'folder', or 'link') and type-specific fields.
Sitemap/channel ID where the page should be created. If not provided, uses the default sitemap for the locale.
Parent page ID for creating child pages.
Page ID to place this page before (for ordering).
Page ID of the created or updated page along with success metadata.
reorder_page_modulesReorders modules within a page zone.
A lightweight alternative to save_page when only the module order needs to change. Validates that all module IDs exist in the zone.
Instance that owns the page.
Locale code such as `en-us`.
The page containing the modules.
The zone to reorder (e.g., 'MainContentZone').
Content IDs in desired order. Must include all existing module IDs in the zone.
Sitemap/channel ID (uses default if not provided).
Confirmation with the new module order and page ID.
Upload images and files from URLs or local paths to the Agility CMS media library.
initialize_media_uploadInitialize a media asset upload and receive a temporary signed URL.
Generates a temporary signed URL that can be used to upload media files to Agility CMS through the /api/uploadAsset endpoint. The URL expires in 5 minutes and can only be used once.
Instance that owns the media library.
Optional file name including extension. If omitted, a name will be generated based on the content type.
Optional media library folder. Defaults to `mcp-uploads`.
Upload signature including `uploadUrl`, `uploadToken`, `expiresAt` timestamp, and usage instructions.