Skip to main content
Glama
webflow

Webflow

Official
by webflow

Create Collection Item

collections_items_create_item

Add new draft items to a Webflow CMS collection for content management and publishing workflows.

Instructions

Create new items in a CMS collection as drafts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes
requestYes

Implementation Reference

  • The handler function that performs the actual work of creating a collection item by calling the Webflow API's createItem method.
    async ({ collection_id, request }) => {
      try {
        const response = await getClient().collections.items.createItem(
          collection_id,
          request,
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • The server.registerTool call that registers the tool with its name, input schema, and handler function.
    server.registerTool(
      "collections_items_create_item",
      {
        title: "Create Collection Item",
        description: "Create new items in a CMS collection as drafts.",
        inputSchema: z.object({
          collection_id: z.string(),
          request: WebflowCollectionsItemsCreateItemRequestSchema,
        }),
      },
      async ({ collection_id, request }) => {
        try {
          const response = await getClient().collections.items.createItem(
            collection_id,
            request,
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Zod schema for the request payload used in the tool's inputSchema, defining the structure of items to create.
    export const WebflowCollectionsItemsCreateItemRequestSchema = z.object({
      items: z.array(CollectionItemPostSingleSchema).optional(),
    });
  • src/mcp.ts:49-49 (registration)
    Top-level call to registerCmsTools, which includes the registration of the collections_items_create_item tool among others.
    registerCmsTools(server, getClient);
  • Related schema for the live version of the create item tool (collections_items_create_item_live). Note: Not the primary tool but closely related.
    export const WebflowCollectionsItemsCreateItemLiveRequestSchema = z.object({
      items: z
        .array(
Behavior2/5

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

With no annotations provided, the description carries full burden but offers limited behavioral insight. It states items are created 'as drafts', hinting at a non-published state, but doesn't cover permissions, rate limits, error handling, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 without waste. Every word earns its place, making it easy to scan and understand 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 tool's complexity (2 parameters with nested objects, no output schema, and no annotations), the description is incomplete. It lacks details on parameter usage, behavioral traits, and output expectations. For a creation tool in a CMS context, more context is needed to guide effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds no parameter details. It doesn't explain what 'collection_id' refers to, the structure of 'request' and 'items', or required fields like 'fieldData' with 'name' and 'slug'. The description fails to provide meaning beyond the bare schema, leaving parameters largely undocumented.

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 new items') and resource ('in a CMS collection'), specifying they are created 'as drafts'. It distinguishes from sibling 'collections_items_create_item_live' by implying draft vs. live creation, though not explicitly named. However, it doesn't fully differentiate from other creation tools like 'collections_create'.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for creating draft items, but doesn't mention prerequisites, when to choose this over 'collections_items_create_item_live', or other sibling tools like 'collections_items_update_items'. Usage context is minimal.

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