Skip to main content
Glama
webflow

Webflow

Official
by webflow

Designer Page Tool

de_page_tool

Manage Webflow site pages by creating pages and folders, switching between pages, and retrieving current page details.

Instructions

Designer Tool - Page tool to perform actions like create page, create page folder, get current page, switch page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesThe ID of the site. DO NOT ASSUME site id. ALWAYS ask user for site id if not already provided or known. use sites_list tool to fetch all sites and then ask user to select one of them.
actionsYes

Implementation Reference

  • Handler function for 'de_page_tool'. Proxies the call to an internal 'page_tool' via RPC and handles response formatting with error catching.
    async ({ siteId, actions }) => {
      try {
        return formatResponse(await pageToolRPCCall(siteId, actions));
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod input schema for 'de_page_tool', defining siteId (via SiteIdSchema) and actions array supporting create_page, create_page_folder, get_current_page, switch_page.
    inputSchema: z.object({
      ...SiteIdSchema,
      actions: z.array(
        z.object({
          create_page: z
            .object({
              page_name: z
                .string()
                .describe("The name of the page to create"),
              meta_title: z
                .string()
                .describe("The meta title of the page to create"),
              meta_description: z
                .string()
                .optional()
                .describe("The meta description of the page to create"),
              page_parent_folder_id: z
                .string()
                .optional()
                .describe(
                  "The id of the parent page folder to create the page in"
                ),
            })
            .optional()
            .describe("Create new page"),
          create_page_folder: z
            .object({
              page_folder_name: z
                .string()
                .describe("The name of the page folder to create"),
              page_folder_parent_id: z
                .string()
                .optional()
                .describe(
                  "The id of the parent page folder to create the page folder in"
                ),
            })
            .optional()
            .describe("Create new page folder"),
    
          get_current_page: z
            .boolean()
            .optional()
            .describe("Get current page active on webflow designer"),
          switch_page: z
            .object({
              page_id: z.string().describe("The id of the page to switch to"),
            })
            .optional()
            .describe("Switch to a page on webflow designer"),
        })
      ),
    }),
  • Registers the 'de_page_tool' on the McpServer with title, description, inputSchema, and handler function.
    server.registerTool(
      "de_page_tool",
      {
        title: "Designer Page Tool",
        description:
          "Designer Tool - Page tool to perform actions like create page, create page folder, get current page, switch page",
        inputSchema: z.object({
          ...SiteIdSchema,
          actions: z.array(
            z.object({
              create_page: z
                .object({
                  page_name: z
                    .string()
                    .describe("The name of the page to create"),
                  meta_title: z
                    .string()
                    .describe("The meta title of the page to create"),
                  meta_description: z
                    .string()
                    .optional()
                    .describe("The meta description of the page to create"),
                  page_parent_folder_id: z
                    .string()
                    .optional()
                    .describe(
                      "The id of the parent page folder to create the page in"
                    ),
                })
                .optional()
                .describe("Create new page"),
              create_page_folder: z
                .object({
                  page_folder_name: z
                    .string()
                    .describe("The name of the page folder to create"),
                  page_folder_parent_id: z
                    .string()
                    .optional()
                    .describe(
                      "The id of the parent page folder to create the page folder in"
                    ),
                })
                .optional()
                .describe("Create new page folder"),
    
              get_current_page: z
                .boolean()
                .optional()
                .describe("Get current page active on webflow designer"),
              switch_page: z
                .object({
                  page_id: z.string().describe("The id of the page to switch to"),
                })
                .optional()
                .describe("Switch to a page on webflow designer"),
            })
          ),
        }),
      },
      async ({ siteId, actions }) => {
        try {
          return formatResponse(await pageToolRPCCall(siteId, actions));
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Helper function that proxies the page tool call to an internal RPC 'page_tool'.
    const pageToolRPCCall = async (siteId: string, actions: any) => {
      return rpc.callTool("page_tool", {
        siteId,
        actions: actions || [],
      });
    };
  • src/mcp.ts:63-63 (registration)
    Top-level call to registerDEPagesTools within registerDesignerTools, which registers 'de_page_tool' among designer tools.
    registerDEPagesTools(server, rpc);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it lists action types, it doesn't describe important behavioral aspects: whether these are read-only or mutating operations (create actions imply writes), what permissions are required, whether actions are atomic or batched, what happens on errors, or what the response format looks like. For a tool with multiple action types including creations, this is a significant transparency 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 reasonably concise at 15 words, front-loading the key information about action types. The structure 'Designer Tool - Page tool to perform actions like...' efficiently communicates scope. However, the phrase 'Designer Tool - Page tool' is somewhat redundant, and the description could be more precisely worded to avoid the vague 'actions like' construction.

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?

For a multi-action tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical contextual aspects: the relationship between the four action types, whether this is for batch operations, what the response contains, error behavior, or how this integrates with the Webflow designer context mentioned in the title. With 2 parameters (one complex) and multiple possible operations, more guidance is needed for 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 50%, with the 'siteId' parameter well-documented but the 'actions' array structure only partially described. The description mentions the four action types (create_page, create_page_folder, get_current_page, switch_page) which maps to the schema's structure, adding some semantic context. However, it doesn't explain whether multiple actions can be performed in one call, the execution order, or error handling - leaving gaps despite the schema's partial documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists specific actions (create page, create page folder, get current page, switch page) which clarifies the tool's purpose beyond just the name/title. However, it doesn't distinguish this tool from sibling tools like 'pages_list' or 'pages_update_page_settings' - it's unclear why this multi-action tool exists alongside more specialized page tools. The phrase 'Designer Tool - Page tool' is somewhat redundant with the title.

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. With sibling tools like 'pages_list', 'pages_get_content', and 'pages_update_page_settings', there's no indication whether this is a comprehensive page management tool or has specific use cases. The description doesn't mention prerequisites, constraints, or typical scenarios for choosing this multi-action approach.

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