Skip to main content
Glama
webflow

Webflow

Official
by webflow

Get Component Content

components_get_content

Retrieve structured content data for Webflow components, including text, images, and nested elements, to integrate component information into external systems.

Instructions

Get the content structure and data for a specific component including text, images, and nested components.

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

  • Handler function that retrieves the content structure and data for a specific component by calling the Webflow API's getContent method.
    async ({ site_id, component_id, localeId, limit, offset }) => {
      try {
        const response = await getClient().components.getContent(
          site_id,
          component_id,
          {
            localeId,
            limit,
            offset,
          },
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod input schema defining parameters for the components_get_content tool: site_id, component_id, optional localeId, limit, and offset.
      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."
          ),
      }),
    },
  • Registration of the 'components_get_content' tool with the MCP server, specifying name, title, description, input schema, and handler function.
    server.registerTool(
      "components_get_content",
      {
        title: "Get Component Content",
        description:
          "Get the content structure and data for a specific component including text, images, and nested components.",
        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.getContent(
            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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves content but doesn't mention whether it's a read-only operation, requires authentication, has rate limits, returns paginated results, or handles errors. The description lacks details on output format, performance, or side effects, which are critical for a tool with multiple parameters and no output schema.

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 front-loads the core purpose ('Get the content structure and data for a specific component') and adds specifics ('including text, images, and nested components'). There's no wasted verbiage or redundancy, making it easy to parse. However, it could be slightly more structured by separating usage hints, but it's appropriately sized for its informational content.

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 (5 parameters, no annotations, no output schema), the description is incomplete. It doesn't address behavioral aspects like read-only nature, authentication needs, or pagination behavior implied by limit/offset parameters. Without annotations or output schema, the description should provide more context on what the tool returns and how to use it effectively, but it falls short, leaving gaps for an AI agent to infer.

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 five parameters (site_id, component_id, localeId, limit, offset) with clear descriptions. The description adds no additional meaning about parameters beyond implying that 'component_id' identifies the target component. It doesn't explain parameter interactions (e.g., how localeId affects content) or provide examples, so it meets the baseline for high schema coverage without compensating further.

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 ('Get') and resource ('content structure and data for a specific component'), specifying it includes text, images, and nested components. This distinguishes it from sibling tools like 'components_get_properties' (which likely gets metadata) and 'components_update_content' (which modifies content). However, it doesn't explicitly contrast with 'pages_get_content' (which might get page-level content), leaving some sibling differentiation incomplete.

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 a valid site_id and component_id), compare it to 'components_get_properties' or 'pages_get_content', or indicate scenarios where it's appropriate (e.g., for rendering component details). Usage is implied only by the tool name and description, with no explicit context or exclusions.

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