Skip to main content
Glama
webflow

Webflow

Official
by webflow

Create Static Field

collection_fields_create_static

Add custom static fields like text, numbers, dates, or images to Webflow CMS collections to structure content with specific data types and requirements.

Instructions

Create a new static field in a CMS collection (e.g., text, number, date, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.
requestYes

Implementation Reference

  • The handler function that executes the tool logic by calling the Webflow API to create a static field in a collection.
    async ({ collection_id, request }) => {
      try {
        const response = await getClient().collections.fields.create(
          collection_id,
          request,
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
  • Registers the 'collection_fields_create_static' tool with the MCP server, defining its title, description, input schema, and handler.
      "collection_fields_create_static",
      {
        title: "Create Static Field",
        description:
          "Create a new static field in a CMS collection (e.g., text, number, date, etc.).",
        inputSchema: z.object({
          collection_id: z
            .string()
            .describe("Unique identifier for the Collection."),
          request: StaticFieldSchema,
        }),
      },
      async ({ collection_id, request }) => {
        try {
          const response = await getClient().collections.fields.create(
            collection_id,
            request,
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Zod schema defining the input parameters for creating a static field (e.g., type, name, required status).
    export const StaticFieldSchema = z.object({
      id: z.string().optional().describe("Unique identifier for the Field."),
      isEditable: z
        .boolean()
        .optional()
        .describe("Indicates if the field is editable."),
      isRequired: z
        .boolean()
        .optional()
        .describe("Indicates if the field is required."),
      type: z
        .union([
          z.literal("Color"),
          z.literal("DateTime"),
          z.literal("Email"),
          z.literal("File"),
          z.literal("Image"),
          z.literal("Link"),
          z.literal("MultiImage"),
          z.literal("Number"),
          z.literal("Phone"),
          z.literal("PlainText"),
          z.literal("RichText"),
          z.literal("Switch"),
          z.literal("Video"),
        ])
        .describe("Type of the field. Choose of these appropriate field types."),
      displayName: z.string().describe("Name of the field."),
      helpText: z.string().optional().describe("Help text for the field."),
    });
  • src/mcp.ts:49-49 (registration)
    Calls registerCmsTools within the main registerTools function, which registers all CMS tools including collection_fields_create_static.
    registerCmsTools(server, getClient);
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 minimal behavioral insight. It states the tool creates a field but doesn't disclose permissions needed, whether the operation is idempotent, what happens on failure, or any rate limits. For a mutation tool with zero annotation coverage, this is inadequate.

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 core purpose. It avoids redundancy but could be more structured by separating purpose from examples or constraints.

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?

For a mutation tool with no annotations, no output schema, and moderate schema coverage, the description is insufficient. It lacks details on behavioral traits, error handling, and usage context, making it incomplete for safe and effective tool invocation.

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%, and the description adds little beyond the schema. It mentions field types (e.g., 'text, number, date') which loosely relates to the 'type' enum in the schema, but doesn't explain parameter interactions or provide additional context. The baseline is 3 since the schema covers parameters moderately well.

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') and resource ('static field in a CMS collection'), with examples of field types provided. It distinguishes from sibling tools like 'collection_fields_create_option' and 'collection_fields_create_reference' by specifying 'static' field creation, though it doesn't explicitly contrast with these alternatives.

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 guidance is provided on when to use this tool versus alternatives like 'collection_fields_create_option' or 'collection_fields_create_reference'. The description mentions field types but doesn't specify prerequisites, constraints, or appropriate contexts for static field creation.

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