Skip to main content
Glama
deenesjakoruzh
webflow

Webflow

Official
by webflow
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get Page Metadata

pages_get_metadata

Retrieve page metadata including SEO settings, Open Graph data, and publication status from Webflow sites to manage content visibility and optimization.

Instructions

Get metadata for a specific page including SEO settings, Open Graph data, and page status (draft/published).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesUnique identifier for the page.
localeIdNoUnique identifier for a specific locale. Applicable when using localization.

Implementation Reference

  • src/tools/pages.ts:66-95 (registration)
    Registration of the 'pages_get_metadata' tool using server.registerTool, including title, description, input schema, and the handler function.
      "pages_get_metadata",
  {
    title: "Get Page Metadata",
    description:
      "Get metadata for a specific page including SEO settings, Open Graph data, and page status (draft/published).",
    inputSchema: z.object({
      page_id: z.string().describe("Unique identifier for the page."),
      localeId: z
        .string()
        .optional()
        .describe(
          "Unique identifier for a specific locale. Applicable when using localization."
        ),
    }),
  },
  async ({ page_id, localeId }) => {
    try {
      const response = await getClient().pages.getMetadata(
        page_id,
        {
          localeId,
        },
        requestOptions
      );
      return formatResponse(response);
    } catch (error) {
      return formatErrorResponse(error);
    }
  }
);
  • src/tools/pages.ts:81-94 (handler)
    The async handler function that executes the tool: fetches page metadata via WebflowClient.pages.getMetadata, formats the response or error.
    async ({ page_id, localeId }) => {
  try {
    const response = await getClient().pages.getMetadata(
      page_id,
      {
        localeId,
      },
      requestOptions
    );
    return formatResponse(response);
  } catch (error) {
    return formatErrorResponse(error);
  }
}
  • src/tools/pages.ts:71-79 (schema)
    Zod inputSchema for the tool, validating page_id (string) and optional localeId (string).
    inputSchema: z.object({
  page_id: z.string().describe("Unique identifier for the page."),
  localeId: z
    .string()
    .optional()
    .describe(
      "Unique identifier for a specific locale. Applicable when using localization."
    ),
}),

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It indicates this is a read operation ('Get'), but doesn't disclose authentication requirements, rate limits, error conditions, or what happens if the page doesn't exist. It mentions the types of metadata returned but not the format or structure. For a read tool with no annotations, this provides basic behavioral context but leaves significant gaps.

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 and includes relevant details. Every word earns its place - no redundancy or unnecessary elaboration. It's appropriately sized for a simple metadata retrieval tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read operation with no annotations and no output schema, the description provides basic context about what metadata is returned. However, it doesn't explain the return format, error handling, or authentication requirements. Given the tool's relative simplicity and the fact that it's a read operation (implied by 'Get'), the description is minimally adequate but leaves room for improvement in behavioral transparency.

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 fully documents both parameters (page_id and localeId). The description doesn't add any parameter-specific information beyond what's in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 verb 'Get' and resource 'metadata for a specific page', specifying what metadata is included (SEO settings, Open Graph data, page status). It distinguishes from sibling tools like pages_get_content (which likely gets content rather than metadata) and pages_list (which lists pages rather than getting metadata for one). However, it doesn't explicitly contrast with all siblings, so it's not a perfect 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by specifying 'for a specific page', suggesting it's used when you need metadata for an individual page rather than listing pages. However, it doesn't explicitly state when to use this tool versus alternatives like pages_get_content or provide any exclusion criteria. The guidance is implied rather than explicit.

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