Webflow

Official

Overview Schema Source Related Servers Discussions Admin

Designer Asset Tool

asset_tool

Manage site assets: create folders, retrieve assets and folders, update asset names and alt text. Organize and modify your Webflow site's asset library.

Instructions

Designer Tool - Asset tool to perform actions like create folder, get all assets and folders, update assets and folders

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>",
      "actions": "<actions>"
    },
    "name": "asset_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.
`actions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Jan 2, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint=false and openWorldHint=true. Description adds no extra behavioral context (e.g., side effects, idempotency, permission needs). Fails to clarify what the 'open world' side effects are.

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

Conciseness3/5

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

Description is one sentence, concise but vaguely worded with 'perform actions like'. Front-loaded with 'Designer Tool -', which is not essential. Could be more precise but is not overly verbose.

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?

Given the tool's complexity (multiple actions via an array), the description is insufficient. No output schema, no explanation of action ordering or response format. The description does not tie the structured input schema to a coherent workflow.

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

Parameters2/5

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

Schema description coverage is 50% but the tool description does not add meaning beyond what the schema provides. siteId has a detailed schema description, but actions and sub-properties are not augmented by the tool description. No compensation for missing schema documentation.

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?

Description states it's an asset tool for actions like create folder, get all assets/folders, update. Clearly indicates the resource (assets) and actions. Distinguishes from siblings like style_tool or component_builder.

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 vs alternatives (e.g., data_cms_tool). No prerequisites or exclusions mentioned. The description simply lists actions without usage context.

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