Webflow

Official

by webflow

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Data Comments Tool

data_comments_tool

Read-only

Retrieve and inspect user feedback comments on Webflow sites. List comment threads, get details, and view replies for design discussions.

Instructions

Data tool - A comment in Webflow is user feedback attached to a specific element or page inside the Designer, stored as a top-level thread with optional replies. Each comment includes author info, timestamps, content, resolved state, and design-context metadata like page location and breakpoint. Use this tool to inspect feedback discussions across the site and understand where and why they were left.

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_comments_tool"
  }
}

Input Schema

Name	Required	Description	Default
`actions`	Yes	The actions to perform on the comments.

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds context about the data included (author info, timestamps, resolved state, design-context metadata), which goes beyond annotations. No behavioral contradictions.

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 three sentences, front-loaded with the tool's role, and every sentence adds value. No wasted words.

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?

The lack of output schema means the description must convey return value info. It describes the comment structure (author, timestamps, content, resolved state, design-context metadata) but could mention the output format for list vs get operations. Still, it provides adequate context for a read-only tool.

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 the input schema already documents the 'actions' parameter and its nested actions. The description provides conceptual context but does not add new meaning to the parameters beyond what the schema provides.

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 tool is for inspecting comment feedback discussions in Webflow Designer, explaining what a comment is and its metadata. It distinguishes itself from sibling tools like data_cms_tool and data_pages_tool by focusing specifically on comments.

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 explicitly says 'Use this tool to inspect feedback discussions' and explains the context (page location, breakpoint). It does not mention when not to use it or provide alternatives, but the context is clear enough for an agent to decide.

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