Skip to main content
Glama
webflow

Webflow

Official
by webflow

Get Site

sites_get

Retrieve detailed information about a Webflow site including settings, domains, and publishing status using its unique identifier.

Instructions

Get detailed information about a specific site including its settings, domains, and publishing status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesUnique identifier for the site.

Implementation Reference

  • Handler function for 'sites_get' tool that retrieves detailed site information using the WebflowClient.
    async ({ site_id }) => {
      try {
        const response = await getClient().sites.get(site_id, requestOptions);
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Input schema for the 'sites_get' tool, defining the required 'site_id' parameter.
    {
      title: "Get Site",
      description:
        "Get detailed information about a specific site including its settings, domains, and publishing status.",
      inputSchema: z.object({
        site_id: z.string().describe("Unique identifier for the site."),
      }),
    },
  • Direct registration of the 'sites_get' tool within registerSiteTools function.
    server.registerTool(
      "sites_get",
      {
        title: "Get Site",
        description:
          "Get detailed information about a specific site including its settings, domains, and publishing status.",
        inputSchema: z.object({
          site_id: z.string().describe("Unique identifier for the site."),
        }),
      },
      async ({ site_id }) => {
        try {
          const response = await getClient().sites.get(site_id, requestOptions);
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • src/mcp.ts:53-53 (registration)
    Top-level registration call that includes the 'sites_get' tool via registerSiteTools.
    registerSiteTools(server, getClient);
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 this is a 'Get' operation, implying it's likely read-only and non-destructive, but doesn't confirm this or add context such as authentication requirements, rate limits, error conditions, or what 'detailed information' entails in the response format. This leaves significant gaps for a tool with no annotation coverage.

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 ('Get detailed information about a specific site') and includes key details ('settings, domains, and publishing status') without unnecessary elaboration. Every word contributes to understanding, making it appropriately concise and well-structured.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and scope but lacks behavioral context (e.g., response format, error handling) and usage guidelines. For a simple read operation, this might suffice, but it doesn't fully compensate for the absence of annotations or output schema, leaving room for improvement.

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?

The input schema has 100% description coverage, with the single parameter 'site_id' documented as 'Unique identifier for the site.' The description adds no additional meaning beyond this, such as format examples or sourcing instructions. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 'site' with specific details ('detailed information about a specific site including its settings, domains, and publishing status'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'sites_list' (which likely lists multiple sites) or 'pages_get_content' (which focuses on page content rather than site metadata), missing full sibling distinction.

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 site_id), exclusions, or comparisons to sibling tools like 'sites_list' for listing sites or 'pages_get_content' for page-specific data, leaving usage context 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