Skip to main content
Glama
webflow

Webflow

Official
by webflow

Publish Site

sites_publish

Publish a Webflow site to specified domains, making the latest changes live on custom domains or Webflow subdomains.

Instructions

Publish a site to specified domains. This will make the latest changes live on the specified domains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesUnique identifier for the site.
customDomainsNoArray of custom domains to publish the site to.
publishToWebflowSubdomainNoWhether to publish to the Webflow subdomain.

Implementation Reference

  • Handler function that publishes the site using WebflowClient.sites.publish API, handling custom domains and Webflow subdomain options.
    async ({ site_id, customDomains, publishToWebflowSubdomain }) => {
      try {
        const response = await getClient().sites.publish(
          site_id,
          {
            customDomains,
            publishToWebflowSubdomain,
          },
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod input schema defining parameters for the sites_publish tool: site_id (required), customDomains (optional array), publishToWebflowSubdomain (optional boolean, default false).
    inputSchema: z.object({
      site_id: z.string().describe("Unique identifier for the site."),
      customDomains: z
        .string()
        .array()
        .optional()
        .describe("Array of custom domains to publish the site to."),
      publishToWebflowSubdomain: z
        .boolean()
        .optional()
        .default(false)
        .describe("Whether to publish to the Webflow subdomain."),
    }),
  • Registration of the sites_publish tool on the MCP server, including schema and handler.
    server.registerTool(
      "sites_publish",
      {
        title: "Publish Site",
        description:
          "Publish a site to specified domains. This will make the latest changes live on the specified domains.",
        inputSchema: z.object({
          site_id: z.string().describe("Unique identifier for the site."),
          customDomains: z
            .string()
            .array()
            .optional()
            .describe("Array of custom domains to publish the site to."),
          publishToWebflowSubdomain: z
            .boolean()
            .optional()
            .default(false)
            .describe("Whether to publish to the Webflow subdomain."),
        }),
      },
      async ({ site_id, customDomains, publishToWebflowSubdomain }) => {
        try {
          const response = await getClient().sites.publish(
            site_id,
            {
              customDomains,
              publishToWebflowSubdomain,
            },
            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 full burden but offers minimal behavioral insight. It states the tool makes changes 'live', implying a write/mutation operation, but doesn't disclose critical traits like whether this is reversible, permission requirements, rate limits, or what happens if domains are invalid. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loaded and efficiently structured in two sentences with zero waste. The first sentence states the core purpose, and the second clarifies the outcome ('make the latest changes live'). Every word earns its place without redundancy or fluff.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral consequences (e.g., whether publishing is destructive to previous versions), error conditions, or what the tool returns. Given the complexity of publishing a site to domains, more context is needed to guide the agent 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 100%, so parameters are well-documented in the schema itself. The description adds marginal value by implying 'customDomains' and 'publishToWebflowSubdomain' are the 'specified domains', but doesn't provide additional semantics like domain format examples or the interplay between these parameters. Baseline 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 action ('Publish') and resource ('a site to specified domains'), specifying it makes 'latest changes live'. It distinguishes from siblings like 'sites_get' or 'sites_list' by focusing on deployment rather than retrieval. However, it doesn't explicitly differentiate from 'collections_items_publish_items' which publishes content items rather than the entire site.

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions 'specified domains' but doesn't clarify prerequisites (e.g., whether domains must be configured first), when not to use it (e.g., if site is already published), or how it relates to siblings like 'collections_items_publish_items'. This leaves the agent without contextual usage direction.

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