Skip to main content
Glama
webflow

Webflow

Official
by webflow

Designer Component Tool

de_component_tool

Create component instances, get all components, transform elements, and manage component metadata in Webflow Designer.

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changed
    • addedInput schema / properties / actions / items / properties / get_component
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Get a component by ID or by name. Provide component_id for ID lookup, or name (and optional group) for name lookup.",
      +  "properties": {
      +    "component_id": {
      +      "description": "The id of the component to get. Use this or name.",
      +      "type": "string"
      +    },
      +    "group": {
      +      "description": "Optional group to narrow the search when using name",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "The name of the component. Use this or component_id.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / actions / items / properties / get_component_metadata
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Get the metadata (name, group, description) of a component",
      +  "properties": {
      +    "component_id": {
      +      "description": "The id of the component",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "component_id"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / properties / actions / items / properties / insert_component_instance / properties / creation_position / description
      Previous value: -"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."New value: +"The position to create component instance on. append/prepend insert as child of the parent element. before/after insert as sibling adjacent to the target element."
    • changedInput schema / properties / actions / items / properties / insert_component_instance / properties / creation_position / enum
      Previous value: -[
      -  "append",
      -  "prepend"
      -]New value: +[
      +  "append",
      +  "prepend",
      +  "before",
      +  "after"
      +]
    • addedInput schema / properties / actions / items / properties / set_component_metadata
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Update metadata (name, group, description) of a component",
      +  "properties": {
      +    "component_id": {
      +      "description": "The id of the component",
      +      "type": "string"
      +    },
      +    "description": {
      +      "description": "New description for the component",
      +      "type": "string"
      +    },
      +    "group": {
      +      "description": "New group for the component",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "New name for the component",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "component_id"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / actions / items / properties / transform_element_to_component / properties / description
      Added value: +{
      +  "description": "Optional description for the component",
      +  "type": "string"
      +}
    • addedInput schema / properties / actions / items / properties / transform_element_to_component / properties / group
      Added value: +{
      +  "description": "Optional group/category for the component",
      +  "type": "string"
      +}
    • addedInput schema / properties / actions / items / properties / unregister_component
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Unregister a component. DANGEROUS ACTION. USE WITH CAUTION.",
      +  "properties": {
      +    "component_id": {
      +      "description": "The id of the component to unregister",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "component_id"
      +  ],
      +  "type": "object"
      +}
  2. Addedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations indicate readOnlyHint: false and openWorldHint: true, but the description does not elaborate on destructive capabilities (e.g., unregister is marked dangerous in schema but not in description). Lacks behavioral context beyond what annotations already provide.

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

Conciseness2/5

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

The description is short but imprecise. It uses vague phrasing like 'and more' without adding clarity. Does not earn its place.

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 (many actions, no output schema), the description fails to explain prerequisites, flow of actions, or return behavior. The schema provides details, but the high-level guidance is missing.

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 50%; the description adds no meaning to parameters. Despite schema having some descriptions, the tool description is silent on how parameters relate to actions.

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

Purpose3/5

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

The description states it can perform actions like creating component instances and getting components, but it is vague ('and more') and does not clearly define the scope or differentiate from sibling tools like 'component_builder' or 'data_components_tool'.

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 on when to use this tool versus alternatives. Sibling tools exist but no differentiation or context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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