Skip to main content
Glama
webflow

Webflow

Official
by webflow

Create Collection

collections_create

Create a new CMS collection in Webflow by defining its name, singular name, and URL slug to organize and structure content on your site.

Instructions

Create a new CMS collection in a site with specified name and schema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesUnique identifier for the Site.
requestYes

Implementation Reference

  • src/tools/cms.ts:75-98 (registration)
    Registration of the 'collections_create' tool, including inline handler that executes the Webflow API call to create a new CMS collection and the input schema definition.
    server.registerTool(
      "collections_create",
      {
        title: "Create Collection",
        description:
          "Create a new CMS collection in a site with specified name and schema.",
        inputSchema: z.object({
          site_id: z.string().describe("Unique identifier for the Site."),
          request: WebflowCollectionsCreateRequestSchema,
        }),
      },
      async ({ site_id, request }) => {
        try {
          const response = await getClient().collections.create(
            site_id,
            request,
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Zod schema for the request body used in the 'collections_create' tool.
    export const WebflowCollectionsCreateRequestSchema = z.object({
      displayName: z
        .string()
        .describe(
          "Name of the collection. Each collection must have a unique name within the site."
        ),
      singularName: z.string().describe("Singular name of the collection."),
      slug: z
        .string()
        .optional()
        .describe("Slug of the collection in the site URL structure. "),
    });
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 of behavioral disclosure. It states it's a creation tool, implying a write operation, but doesn't cover critical aspects like permissions required, whether the operation is idempotent, rate limits, or what happens on failure (e.g., duplicate names). The description adds minimal value beyond the basic action, leaving significant gaps for a mutation tool.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the key action and parameters. There's no wasted verbiage, and it directly addresses the tool's purpose. However, it could be slightly more structured by explicitly listing parameters or adding usage notes without sacrificing conciseness.

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 complexity (a write operation with nested parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., the new collection's ID), error conditions, or behavioral nuances. For a creation tool in a CMS context, more detail is needed to guide effective use by an AI agent.

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 50% (2 parameters total: 'site_id' and 'request', with 'request' being a nested object). The description mentions 'name and schema', which loosely maps to 'displayName' and potentially other fields in 'request', but doesn't clarify the meaning of 'schema' or detail the nested structure. It adds some context over the schema but doesn't fully compensate for the coverage gap, especially for 'singularName' and 'slug'.

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 ('Create a new CMS collection') and the resource ('in a site'), specifying the required parameters ('with specified name and schema'). It distinguishes from siblings like 'collections_list' or 'collections_get' by focusing on creation. However, it doesn't explicitly differentiate from other creation tools like 'collection_fields_create_option' or 'collections_items_create_item', which target different resources.

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. It doesn't mention prerequisites (e.g., needing an existing site), exclusions (e.g., not for updating collections), or comparisons to sibling tools like 'collections_list' for reading or 'collection_fields_create_option' for related operations. Usage is implied by the verb 'Create' but lacks explicit context.

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