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 so you can understand available content areas before fetching or saving content.
The target Agility instance.
Array of container definitions including display name, ID, reference name, and category.
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 a single content item by ID.
Returns a complete record including system properties, field values, SEO info, and scripts for detailed inspection.
Instance that owns the item.
Content item ID to fetch.
Locale code such as `en-us`.
Full content item object with properties, fields, SEO configuration, and scripts where available.
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/channel by name.
Returns the complete page hierarchy for a specific digital channel, including page IDs, URLs, page types, and dynamic content configurations. Essential for understanding site structure and navigation for a particular channel.
Instance that owns the sitemap.
Locale code such as `en-us`.
Channel/sitemap name to retrieve. This is required.
Digital channel with nested page hierarchies including page IDs, URLs, types, and dynamic content references for the specified channel.
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_pageCreates or updates a page in Agility CMS.
Supports creating and updating static, dynamic, folder, and link pages.
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.
save_content_itemsCreates or updates one or more content items in a container.
Accepts an array of items, allowing a mix of new (`contentID: 0`) and existing records. Handles workflow dates and field value variations including attachments.
Instance that owns the content.
Locale code such as `en-us`.
Array of content items including `contentID`, `referenceName`, `fields`, and optional workflow properties.
Array of content IDs that were saved along with success metadata in `structuredContent`.
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.
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.