Skip to main content
Glama
webflow

Webflow

Official
by webflow

List Collections

collections_list

Retrieve all CMS collections from a Webflow site to view collection metadata, IDs, names, and schemas for content management.

Instructions

List all CMS collections in a site. Returns collection metadata including IDs, names, and schemas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesUnique identifier for the Site.

Implementation Reference

  • The handler function for the 'collections_list' tool. It uses the WebflowClient to list collections for the given site_id and formats the response or error.
    async ({ site_id }) => {
      try {
        const response = await getClient().collections.list(
          site_id,
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Input schema for the 'collections_list' tool, requiring a site_id string parameter.
    inputSchema: z.object({
      site_id: z.string().describe("Unique identifier for the Site."),
    }),
  • src/tools/cms.ts:25-46 (registration)
    Registration of the 'collections_list' tool with the MCP server, including title, description, input schema, and handler function.
    server.registerTool(
      "collections_list",
      {
        title: "List Collections",
        description:
          "List all CMS collections in a site. Returns collection metadata including IDs, names, and schemas.",
        inputSchema: z.object({
          site_id: z.string().describe("Unique identifier for the Site."),
        }),
      },
      async ({ site_id }) => {
        try {
          const response = await getClient().collections.list(
            site_id,
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions the return format ('collection metadata including IDs, names, and schemas') but omits critical behavioral details such as pagination, rate limits, authentication requirements, error handling, or whether it's a read-only operation. This leaves significant gaps for an AI agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose and includes key output details. Every word contributes value without redundancy, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It covers the basic purpose and output structure but misses behavioral aspects like pagination, error cases, or side effects. For a tool with no structured safety or output information, more context is needed to ensure reliable use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents the single parameter 'site_id'. The description adds no additional parameter semantics beyond implying the tool operates within a site context, which is already covered by the schema. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List all CMS collections') and resource ('in a site'), with specific output details ('collection metadata including IDs, names, and schemas'). However, it does not explicitly differentiate from sibling tools like 'collections_get' or 'collections_items_list_items', which handle specific collections or items rather than all collections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as 'collections_get' for a single collection or 'collections_items_list_items' for items within collections. It lacks context on prerequisites or exclusions, relying solely on the implicit need for a site_id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/webflow/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server