Skip to main content
Glama
webflow

Webflow

Official
by webflow

List Sites

sites_list

Retrieve a list of all Webflow sites accessible to your account, including site IDs, names, and last published dates.

Instructions

List all sites accessible to the authenticated user. Returns basic site information including site ID, name, and last published date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler function for the 'sites_list' tool. It calls the WebflowClient.sites.list() method to fetch all accessible sites and formats the response or error.
    async () => {
      try {
        const response = await getClient().sites.list(requestOptions);
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Input schema for the 'sites_list' tool, which takes no parameters (empty object).
    inputSchema: z.object({}),
  • Registers the 'sites_list' tool on the MCP server within the registerSiteTools function, specifying name, metadata, input schema, and handler.
    server.registerTool(
      "sites_list",
      {
        title: "List Sites",
        description:
          "List all sites accessible to the authenticated user. Returns basic site information including site ID, name, and last published date.",
        inputSchema: z.object({}),
      },
      async () => {
        try {
          const response = await getClient().sites.list(requestOptions);
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • src/mcp.ts:53-53 (registration)
    Top-level call to registerSiteTools during MCP server tools registration, which includes the 'sites_list' tool.
    registerSiteTools(server, getClient);
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 discloses that the tool returns basic site information (ID, name, last published date) and implies it's a read operation ('List'), but lacks details on pagination, rate limits, authentication requirements beyond 'authenticated user', or error handling. It adds some behavioral context but leaves gaps for a list operation.

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, well-structured sentence that front-loads the core action ('List all sites accessible to the authenticated user') and adds essential details about the return values. Every word contributes meaning without redundancy, making it efficient and easy to parse.

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

Completeness4/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 (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and what it returns, but could improve by adding more behavioral context (e.g., pagination, sorting) or explicit usage guidelines versus siblings. It's adequate but has minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't mention any parameters, which is appropriate. Baseline is 4 for 0 parameters, as it avoids unnecessary repetition and focuses on the tool's purpose.

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

Purpose5/5

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

The description clearly states the verb ('List') and resource ('sites'), specifies the scope ('accessible to the authenticated user'), and distinguishes from siblings like 'sites_get' (which retrieves a single site) and 'sites_publish' (which modifies sites). It provides specific details about what gets returned, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description implies usage context by mentioning 'authenticated user' and 'accessible' sites, suggesting it's for viewing available sites. However, it doesn't explicitly state when to use this versus alternatives like 'sites_get' (for single site details) or 'collections_list' (for site collections), leaving some ambiguity in sibling differentiation.

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