Skip to main content
Glama
webflow

Webflow

Official
by webflow

Update Component Properties

components_update_properties

Update component properties for localization to customize behavior in different languages on Webflow sites.

Instructions

Update component properties for localization to customize behavior in different languages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesUnique identifier for the Site.
component_idYesUnique identifier for the Component.
localeIdYesUnique identifier for a specific locale. Applicable when using localization.
propertiesYesArray of properties to update for this component.

Implementation Reference

  • The handler function that performs the tool logic: calls WebflowClient.components.updateProperties API with site_id, component_id, localeId, and properties, then formats the response or error.
    async ({ site_id, component_id, localeId, properties }) => {
      try {
        const response = await getClient().components.updateProperties(
          site_id,
          component_id,
          {
            localeId,
            properties,
          },
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Registers the 'components_update_properties' tool on the MCP server, defining its title, description, input schema, and handler function.
    server.registerTool(
      "components_update_properties",
      {
        title: "Update Component Properties",
        description:
          "Update component properties for localization to customize behavior in different languages.",
        inputSchema: z.object({
          site_id: z.string().describe("Unique identifier for the Site."),
          component_id: z
            .string()
            .describe("Unique identifier for the Component."),
          localeId: z
            .string()
            .describe(
              "Unique identifier for a specific locale. Applicable when using localization."
            ),
          properties: ComponentPropertyUpdateSchema,
        }),
      },
      async ({ site_id, component_id, localeId, properties }) => {
        try {
          const response = await getClient().components.updateProperties(
            site_id,
            component_id,
            {
              localeId,
              properties,
            },
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Zod schema defining the 'properties' input: an array of objects each with 'propertyId' (string) and 'text' (string) for updating component properties.
    export const ComponentPropertyUpdateSchema = z
      .array(
        z.object({
          propertyId: z.string().describe("Unique identifier for the property."),
          text: z.string().describe("New value for the property in this locale."),
        })
      )
      .describe("Array of properties to update for this component.");
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. It states this is an update operation for localization, implying mutation, but doesn't disclose critical behavioral traits such as required permissions, whether changes are reversible, rate limits, or what happens to existing properties not mentioned. For a mutation tool with zero annotation coverage, this is a significant gap.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, though it could be slightly more informative given the lack of annotations and output schema.

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 complexity of a mutation tool with no annotations, no output schema, and 4 required parameters, the description is incomplete. It doesn't address behavioral aspects like permissions, side effects, or response format, leaving significant gaps for an AI agent to understand how to use this tool safely and effectively.

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 four parameters thoroughly. The description adds minimal value beyond the schema by implying that 'localeId' and 'properties' are used for localization updates, but it doesn't provide additional syntax, format details, or examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 component properties') and purpose ('for localization to customize behavior in different languages'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'components_update_content' or 'components_get_properties', which might handle similar resources but different operations.

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 mentions 'for localization' which provides some context, but it doesn't offer explicit guidance on when to use this tool versus alternatives (e.g., 'components_update_content' for non-localized updates or 'components_get_properties' for reading properties). No exclusions, prerequisites, or comparative usage scenarios are provided.

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