Skip to main content
Glama
webflow

Webflow

Official
by webflow

Designer Component Tool

de_component_tool

Manage Webflow components by creating instances, transforming elements, renaming components, and viewing all components in a site.

Instructions

Designer tool - Component tool to perform actions like create component instances, get all components and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesThe ID of the site. DO NOT ASSUME site id. ALWAYS ask user for site id if not already provided or known. use sites_list tool to fetch all sites and then ask user to select one of them.
actionsYes

Implementation Reference

  • Handler function for the 'de_component_tool' that calls the helper function componentsToolRPCCall, which invokes the underlying 'component_tool' via RPC, and formats the response or error.
    async ({ siteId, actions }) => {
      try {
        return formatResponse(await componentsToolRPCCall(siteId, actions));
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Input schema for de_component_tool defining siteId and actions array with various component operations using Zod.
    inputSchema: z.object({
      ...SiteIdSchema,
      actions: z.array(
        z.object({
          check_if_inside_component_view: z
            .boolean()
            .optional()
            .describe(
              "Check if inside component view. this helpful to make changes to the component"
            ),
          transform_element_to_component: z
            .object({
              ...DEElementIDSchema,
              name: z.string().describe("The name of the component"),
            })
            .optional()
            .describe("Transform an element to a component"),
          insert_component_instance: z
            .object({
              parent_element_id: DEElementIDSchema.id,
              component_id: z
                .string()
                .describe("The id of the component to insert"),
              creation_position: z
                .enum(["append", "prepend"])
                .describe(
                  "The position to create component instance on. append to the end of the parent element or prepend to the beginning of the parent element. as child of the parent element."
                ),
            })
            .optional()
            .describe("Insert a component on current active page."),
          open_component_view: z
            .object({
              component_instance_id: DEElementIDSchema.id,
            })
            .optional()
            .describe(
              "Open a component instance view for changes or reading."
            ),
          close_component_view: z
            .boolean()
            .optional()
            .describe(
              "Close a component instance view. it will close and open the page view."
            ),
          get_all_components: z
            .boolean()
            .optional()
            .describe(
              "Get all components, only valid if you are connected to Webflow Designer."
            ),
          rename_component: z
            .object({
              component_id: z
                .string()
                .describe("The id of the component to rename"),
              new_name: z.string().describe("The name of the component"),
            })
            .optional()
            .describe("Rename a component."),
        })
      ),
    }),
  • Registration of the 'de_component_tool' using McpServer.registerTool, including title, description, input schema, and handler function.
    server.registerTool(
      "de_component_tool",
      {
        title: "Designer Component Tool",
        description:
          "Designer tool - Component tool to perform actions like create component instances, get all components and more.",
        inputSchema: z.object({
          ...SiteIdSchema,
          actions: z.array(
            z.object({
              check_if_inside_component_view: z
                .boolean()
                .optional()
                .describe(
                  "Check if inside component view. this helpful to make changes to the component"
                ),
              transform_element_to_component: z
                .object({
                  ...DEElementIDSchema,
                  name: z.string().describe("The name of the component"),
                })
                .optional()
                .describe("Transform an element to a component"),
              insert_component_instance: z
                .object({
                  parent_element_id: DEElementIDSchema.id,
                  component_id: z
                    .string()
                    .describe("The id of the component to insert"),
                  creation_position: z
                    .enum(["append", "prepend"])
                    .describe(
                      "The position to create component instance on. append to the end of the parent element or prepend to the beginning of the parent element. as child of the parent element."
                    ),
                })
                .optional()
                .describe("Insert a component on current active page."),
              open_component_view: z
                .object({
                  component_instance_id: DEElementIDSchema.id,
                })
                .optional()
                .describe(
                  "Open a component instance view for changes or reading."
                ),
              close_component_view: z
                .boolean()
                .optional()
                .describe(
                  "Close a component instance view. it will close and open the page view."
                ),
              get_all_components: z
                .boolean()
                .optional()
                .describe(
                  "Get all components, only valid if you are connected to Webflow Designer."
                ),
              rename_component: z
                .object({
                  component_id: z
                    .string()
                    .describe("The id of the component to rename"),
                  new_name: z.string().describe("The name of the component"),
                })
                .optional()
                .describe("Rename a component."),
            })
          ),
        }),
      },
      async ({ siteId, actions }) => {
        try {
          return formatResponse(await componentsToolRPCCall(siteId, actions));
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Helper function that proxies the call to the core 'component_tool' RPC method with prepared arguments.
    const componentsToolRPCCall = async (siteId: string, actions: any) => {
      return rpc.callTool("component_tool", {
        siteId,
        actions: actions || [],
      });
    };
  • src/mcp.ts:61-61 (registration)
    Top-level call to registerDEComponentsTools function, which in turn registers the 'de_component_tool'.
    registerDEComponentsTools(server, rpc);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'perform actions' but doesn't specify whether these are read-only or mutating operations, what permissions are required, or what side effects occur. The description fails to disclose critical behavioral traits like whether changes are destructive, require authentication, or have rate limits.

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

Conciseness3/5

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

The description is brief (one sentence) but inefficiently structured. It starts with redundant phrasing ('Designer tool - Component tool') and uses vague language ('and more'). While concise, it fails to front-load the most critical information about what this tool actually does.

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 complex tool with 2 parameters (one being a complex actions array), no annotations, and no output schema, the description is severely inadequate. It doesn't explain the relationship between different actions, what the tool returns, or how to interpret results. The description fails to provide the necessary context for effective tool use.

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?

The description provides no parameter information beyond what's in the schema. With 50% schema description coverage (siteId is well-documented but actions array lacks overall description), the description doesn't compensate for the coverage gap. However, the schema itself documents the complex actions structure reasonably well, establishing a baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'perform actions like create component instances, get all components and more' which is vague about the specific verb and resource. It lists examples but doesn't clearly define the tool's primary function. While it mentions 'Designer tool - Component tool', this is essentially a restatement of the name and title rather than a clear purpose statement.

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. With sibling tools like 'components_list', 'components_get_content', 'components_update_content', and 'de_page_tool' available, there's no indication of when this multi-action tool is preferred over more specialized tools. No context about prerequisites or constraints is mentioned.

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