Skip to main content
Glama
webflow

Webflow

Official
by webflow

Update Page Settings

pages_update_page_settings

Modify page settings in Webflow to update SEO metadata, Open Graph data, slugs, and publishing status for improved search visibility and content management.

Instructions

Update page settings including SEO metadata, Open Graph data, slug, and publishing status.

Input Schema

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

Implementation Reference

  • The handler function that performs the actual tool logic: calls the Webflow API to update page settings using the provided page_id, localeId, and body.
    async ({ page_id, localeId, body }) => {
      try {
        const response = await getClient().pages.updatePageSettings(
          page_id,
          {
            localeId,
            body,
          },
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Registers the "pages_update_page_settings" tool with the MCP server, including title, description, input schema, and handler function.
    server.registerTool(
      "pages_update_page_settings",
      {
        title: "Update Page Settings",
        description:
          "Update page settings including SEO metadata, Open Graph data, slug, and publishing status.",
        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."
            ),
          body: WebflowPageSchema,
        }),
      },
      async ({ page_id, localeId, body }) => {
        try {
          const response = await getClient().pages.updatePageSettings(
            page_id,
            {
              localeId,
              body,
            },
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Zod schema used for validating the 'body' parameter in the tool's input schema, defining page properties like id, title, slug, SEO, Open Graph, etc.
    export const WebflowPageSchema = z.object({
      id: z.string().describe("Unique identifier for a Page."),
      siteId: z.string().optional().describe("Unique identifier for the Site."),
      title: z.string().optional().describe("Title of the page."),
      slug: z
        .string()
        .optional()
        .describe("Slug of the page (derived from title)."),
      parentId: z
        .string()
        .optional()
        .describe("Unique identifier for the parent folder."),
      collectionId: z
        .string()
        .optional()
        .describe(
          "Unique identifier for the linked collection, NULL id the Page is not part of a collection."
        ),
      createdOn: z.date().optional().describe("Date when the page was created."),
      lastUpdated: z
        .date()
        .optional()
        .describe("Date when the page was last updated."),
      archived: z
        .boolean()
        .optional()
        .describe("Indicates if the page is archived."),
      draft: z.boolean().optional().describe("Indicates if the page is a draft."),
      canBranch: z
        .boolean()
        .optional()
        .describe("Indicates if the page can be branched."),
      isBranch: z
        .boolean()
        .optional()
        .describe("Indicates if the page is Branch of another page."),
      isMembersOnly: z
        .boolean()
        .optional()
        .describe(
          "Indicates whether the Page is restricted by Memberships Controls."
        ),
      seo: z
        .object({
          title: z
            .string()
            .optional()
            .describe("The Page title shown in search engine results."),
          description: z
            .string()
            .optional()
            .describe("The Page description shown in search engine results."),
        })
        .optional()
        .describe("SEO-related fields for the page."),
      openGraph: z
        .object({
          title: z
            .string()
            .optional()
            .describe("The title supplied to Open Graph annotations."),
          titleCopied: z
            .boolean()
            .optional()
            .describe(
              "Indicates the Open Graph title was copied from the SEO title."
            ),
          description: z
            .string()
            .optional()
            .describe("The description supplied to Open Graph annotations."),
          descriptionCopied: z
            .boolean()
            .optional()
            .describe(
              "Indicates the Open Graph description was copied from the SEO description."
            ),
        })
        .optional(),
      localeId: z
        .string()
        .optional()
        .describe(
          "Unique identifier for the page locale. Applicable when using localization."
        ),
      publishedPath: z
        .string()
        .optional()
        .describe("Relative path of the published page."),
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is an update operation (implying mutation) but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens to unspecified settings. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 ('Update page settings') followed by specific examples. There is zero waste—every word contributes to understanding what the tool does. It's appropriately sized for a tool with a clear scope.

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 (mutation with nested objects), lack of annotations, and no output schema, the description is insufficient. It doesn't cover error conditions, response format, or important behavioral aspects like idempotency or side effects. For a tool that modifies page settings, more context is needed to use it 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 67%, providing moderate documentation. The description lists examples of updatable fields (SEO metadata, Open Graph data, slug, publishing status), which partially maps to the 'body' parameter's nested properties. However, it doesn't add significant meaning beyond what the schema already describes (e.g., it doesn't explain how these fields interact or formatting requirements). With schema coverage above 50%, the baseline is met but not exceeded.

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 ('Update') and resource ('page settings') with specific examples of what can be updated (SEO metadata, Open Graph data, slug, publishing status). It distinguishes this tool from sibling tools like 'pages_get_content' or 'pages_update_static_content' by focusing on settings rather than content. However, it doesn't explicitly differentiate from all possible siblings in the list.

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 page_id), when not to use it (e.g., for content updates vs. settings), or refer to sibling tools like 'pages_update_static_content' for comparison. Usage is implied but not explicitly stated.

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