Webflow

Official

by webflow

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

element_snapshot_tool

Read-only

Capture a snapshot of any Webflow element to inspect its state, useful for debugging and visual feedback.

Instructions

Designer Tool - Element snapshot tool to perform actions like get element snapshot. helpful to get element snapshot for debugging and more and visual feedback.

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": {
      "siteId": "<siteId>",
      "action": "<action>"
    },
    "name": "element_snapshot_tool"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes	The ID of the site. DO NOT ASSUME site id. ALWAYS ask user for site id if not already provided or known. use sites_list tool to fetch all sites and then ask user to select one of them.
`action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 5, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint: true, so the agent knows this tool is read-only. The description adds minimal behavioral context beyond that, such as 'snapshot for debugging,' but does not disclose details like error handling or output format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that redundantly mentions 'element snapshot' twice and is poorly structured. It lacks clarity and could be significantly condensed.

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?

The description does not explain the return value or behavior of the snapshot, which is problematic since there is no output schema. It also fails to provide enough detail for a tool with nested parameters, leaving the agent to infer usage.

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 provides decent explanations for both parameters (siteId and action), with siteId having a detailed instruction. The description adds no additional information about the parameters beyond what the schema already provides.

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?

The description states it is a 'Designer Tool' for 'get element snapshot' and mentions debugging and visual feedback, giving a general sense of purpose. However, it is vague and does not clearly distinguish this tool from sibling tools like 'element_tool' or 'de_element_tool', which may have overlapping functionality.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for debugging and visual feedback but provides no conditions, exclusions, or references to sibling tools.

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