Skip to main content
Glama
webflow

Webflow

Official
by webflow

Update Collection Field

collection_fields_update

Modify field properties in Webflow CMS collections to update requirements, display names, or help text for improved content management.

Instructions

Update properties of an existing field in a CMS collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.
field_idYesUnique identifier for the Field.
requestYesRequest schema to update collection field metadata.

Implementation Reference

  • The handler function that executes the tool logic by calling the Webflow API to update a specific field in a collection and handles the response or error.
    async ({ collection_id, field_id, request }) => {
      try {
        const response = await getClient().collections.fields.update(
          collection_id,
          field_id,
          request,
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod schema defining the request body for updating collection field metadata (isRequired, displayName, helpText). Used in the tool's inputSchema.
    export const WebflowCollectionsFieldUpdateSchema = z
      .object({
        isRequired: z
          .boolean()
          .optional()
          .describe("Indicates if the field is required in a collection."),
        displayName: z.string().optional().describe("Name of the field."),
        helpText: z.string().optional().describe("Help text for the field."),
      })
      .describe("Request schema to update collection field metadata.");
  • MCP tool registration for 'collection_fields_update', including name, title, description, composed inputSchema (with collection_id, field_id, and WebflowCollectionsFieldUpdateSchema), and inline handler.
    server.registerTool(
      "collection_fields_update",
      {
        title: "Update Collection Field",
        description:
          "Update properties of an existing field in a CMS collection.",
        inputSchema: z.object({
          collection_id: z
            .string()
            .describe("Unique identifier for the Collection."),
          field_id: z.string().describe("Unique identifier for the Field."),
          request: WebflowCollectionsFieldUpdateSchema,
        }),
      },
      async ({ collection_id, field_id, request }) => {
        try {
          const response = await getClient().collections.fields.update(
            collection_id,
            field_id,
            request,
            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 of behavioral disclosure. It states 'Update properties' implying a mutation, but doesn't disclose permissions needed, whether changes are reversible, rate limits, or what happens to unspecified properties. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, 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 tool's complexity (mutation with nested objects), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, error conditions, or return values, which are crucial for safe and 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 100%, so the schema already documents all parameters (collection_id, field_id, request with isRequired, displayName, helpText). The description adds no additional meaning beyond the schema, such as examples or constraints, but since the schema is comprehensive, the baseline score of 3 is appropriate.

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 ('Update properties') and resource ('existing field in a CMS collection'), making the purpose understandable. However, it does not differentiate this tool from sibling tools like 'collection_fields_create_option' or 'collections_items_update_items', which might also modify collection-related data, so it doesn't fully distinguish from 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing collection and field), exclusions, or compare it to sibling tools like 'collection_fields_create_static' or 'collections_items_update_items', leaving the agent without context for selection.

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