Webflow

Official

by webflow

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Data Sites Tool

data_sites_tool

List Webflow sites, retrieve site details, and publish sites to specified domains.

Instructions

Data tool - Sites tool to perform actions like list sites, get site details, and publish sites

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": {
      "actions": "<actions>"
    },
    "name": "data_sites_tool"
  }
}

Input Schema

Name	Required	Description	Default
`actions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 5, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations indicate non-read-only and open-world hints, and description mentions 'publish' implying mutation. However, no details on side effects, permissions, or irreversible consequences are given.

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?

Single sentence efficiently lists key actions without wordiness. Could benefit from slightly more structure but remains concise.

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?

Description lacks context on return values, error handling, or when to use specific actions. With no output schema, more explanatory text is needed for complete understanding.

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 descriptions are comprehensive for each action, covering required fields and purposes. Baseline of 3 is appropriate as tool description adds no parameter information beyond schema.

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?

Description lists three actions (list, get, publish) but fails to clearly define the tool's overarching purpose or distinguish it from sibling tools like data_pages_tool. The phrase 'Data tool - Sites tool' is redundant and vague.

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 on when to use this tool versus alternatives, no prerequisites or exclusions provided. The description simply enumerates actions without context.

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