Skip to main content
Glama
webflow

Webflow

Official
by webflow

Get Collection

collections_get

Retrieve detailed schema and field definitions for a specific CMS collection in Webflow to understand its structure and data organization.

Instructions

Get detailed information about a specific CMS collection including its schema and field definitions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.

Implementation Reference

  • Handler function for the 'collections_get' tool. Fetches detailed information about a specific CMS collection using the WebflowClient API and formats the response.
    async ({ collection_id }) => {
      try {
        const response = await getClient().collections.get(
          collection_id,
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Input schema for the 'collections_get' tool, defining the required 'collection_id' parameter.
    {
      title: "Get Collection",
      description:
        "Get detailed information about a specific CMS collection including its schema and field definitions.",
      inputSchema: z.object({
        collection_id: z
          .string()
          .describe("Unique identifier for the Collection."),
      }),
    },
  • src/tools/cms.ts:49-72 (registration)
    Registration of the 'collections_get' MCP tool, including schema and handler within the registerCmsTools function.
    server.registerTool(
      "collections_get",
      {
        title: "Get Collection",
        description:
          "Get detailed information about a specific CMS collection including its schema and field definitions.",
        inputSchema: z.object({
          collection_id: z
            .string()
            .describe("Unique identifier for the Collection."),
        }),
      },
      async ({ collection_id }) => {
        try {
          const response = await getClient().collections.get(
            collection_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 states the tool retrieves information, implying it is read-only, but does not disclose behavioral traits such as authentication needs, rate limits, error conditions, or what happens if the collection_id is invalid. For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 purpose ('Get detailed information') and specifies the scope ('including its schema and field definitions'). There is no wasted text, making it appropriately sized and structured.

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

Completeness3/5

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

Given the tool has one parameter with full schema coverage, no output schema, and no annotations, the description is adequate for a simple read operation but incomplete. It lacks details on output format (e.g., what 'detailed information' includes), error handling, or prerequisites, which are important for contextual understanding despite the low complexity.

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%, with the single parameter 'collection_id' well-documented in the schema. The description does not add meaning beyond the schema (e.g., format examples or constraints), so it meets the baseline of 3 for high schema coverage without extra param info.

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 verb ('Get') and resource ('detailed information about a specific CMS collection'), specifying it includes schema and field definitions. However, it does not explicitly differentiate from sibling tools like 'collections_list' (which likely lists collections rather than getting details of one) or 'collection_fields_create_option' (which creates fields rather than retrieving them), though the specificity implies distinction.

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

Usage Guidelines3/5

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

The description implies usage when detailed collection information is needed, but does not explicitly state when to use this tool versus alternatives (e.g., 'collections_list' for listing collections or 'sites_get' for site details). It provides context for retrieving schema and fields but lacks explicit when-not or alternative guidance.

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