Skip to main content
Glama

webflow_get_site

Read-onlyIdempotent

Retrieve a single Webflow site by ID or saved default using a Webflow API token.

Instructions

Get a single Webflow site by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "access_token": "<access_token>"
    },
    "name": "webflow_get_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoWebflow site id (can be a saved default)
access_tokenYesWebflow API token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond the annotations: no statement about what happens when the site id is invalid or whether the response includes nested collections.

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?

A single eight-word sentence with the identifier constraint front-loaded and no wasted clauses. Its brevity is efficient rather than padded, though it leaves little room for the guidance an agent actually needs.

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?

For a two-parameter read tool with full schema coverage, complete annotations, and no output schema, the description covers the essentials of what it does. It is still missing where the site_id comes from and what the call returns, which matter for a chained workflow starting at webflow_list_sites.

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 both parameters (site_id and access_token) are already documented, including the useful "can be a saved default" note for site_id. The description's "by id" merely echoes the schema and adds no format or sourcing detail, so baseline 3 applies.

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?

States a specific verb ("Get") and resource ("a single Webflow site") scoped to a single record by id, which implicitly distinguishes it from webflow_list_sites. It stops short of naming the sibling list tool explicitly, so an agent must infer the boundary.

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?

There is no guidance on when to use this instead of webflow_list_sites, and no indication that a site_id must first be obtained from the list tool. The phrase "by id" weakly implies a prerequisite but nothing is spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools