Skip to main content
Glama
webflow

Webflow

Official
by webflow

Get Component Properties

components_get_properties

Retrieve component properties, default values, and configuration details from Webflow sites to understand and manage component behavior.

Instructions

Get component properties including default values and configuration for a specific component.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesUnique identifier for the Site.
component_idYesUnique identifier for the Component.
localeIdNoUnique identifier for a specific locale. Applicable when using localization.
limitNoMaximum number of records to be returned (max limit: 100)
offsetNoOffset used for pagination if the results have more than limit records.

Implementation Reference

  • The handler function that implements the core logic of the 'components_get_properties' tool by fetching properties from the Webflow API.
    async ({ site_id, component_id, localeId, limit, offset }) => {
      try {
        const response = await getClient().components.getProperties(
          site_id,
          component_id,
          {
            localeId,
            limit,
            offset,
          },
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod input schema defining the parameters for the 'components_get_properties' tool: site_id (required), component_id (required), localeId/limit/offset (optional).
    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()
        .optional()
        .describe(
          "Unique identifier for a specific locale. Applicable when using localization."
        ),
      limit: z
        .number()
        .optional()
        .describe(
          "Maximum number of records to be returned (max limit: 100)"
        ),
      offset: z
        .number()
        .optional()
        .describe(
          "Offset used for pagination if the results have more than limit records."
        ),
    }),
  • The server.registerTool call that registers the 'components_get_properties' tool with its schema and handler function.
    server.registerTool(
      "components_get_properties",
      {
        title: "Get Component Properties",
        description:
          "Get component properties including default values and configuration for a specific component.",
        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()
            .optional()
            .describe(
              "Unique identifier for a specific locale. Applicable when using localization."
            ),
          limit: z
            .number()
            .optional()
            .describe(
              "Maximum number of records to be returned (max limit: 100)"
            ),
          offset: z
            .number()
            .optional()
            .describe(
              "Offset used for pagination if the results have more than limit records."
            ),
        }),
      },
      async ({ site_id, component_id, localeId, limit, offset }) => {
        try {
          const response = await getClient().components.getProperties(
            site_id,
            component_id,
            {
              localeId,
              limit,
              offset,
            },
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
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 indicates this is a read operation ('Get'), but lacks details on permissions, rate limits, pagination behavior (implied by 'limit' and 'offset' parameters but not explained), or what happens with invalid inputs. For a tool with 5 parameters and no annotation coverage, this is insufficient.

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 front-loads the core purpose without unnecessary words. Every part earns its place by specifying what is retrieved and for what resource, 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 (5 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain the return format, error conditions, or behavioral nuances like pagination. For a tool that likely returns structured data about component properties, more context is needed to guide effective 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?

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't clarify relationships between parameters like 'site_id' and 'component_id'). The baseline score of 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 tool's purpose: 'Get component properties including default values and configuration for a specific component.' It specifies the verb ('Get'), resource ('component properties'), and scope ('for a specific component'). However, it doesn't explicitly differentiate from sibling tools like 'components_get_content' or 'components_update_properties', which prevents a perfect score.

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 sibling tools like 'components_get_content' (which might retrieve different data) or 'components_update_properties' (for modifications), nor does it specify prerequisites or exclusions. This leaves the agent with minimal context for tool 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