Skip to main content
Glama
the-real-talk

the-real-talk

clear_fills

Removes every fill from a specified node, so you can reset its appearance or clear unwanted colors in Figma.

Instructions

Remove all fills of a node.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "clear_fills"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesID of the node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the scope of destruction ('all fills', not one fill), but it omits whether the change is reversible, whether it touches inherited or style-bound fills, and what errors occur if the node lacks fills. For a destructive operation, that leaves significant gaps.

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?

One short sentence with the action and the object front-loaded, and no wasted wording. There is nothing to trim and nothing buried.

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?

This is a simple one-parameter mutation with no output schema, so the description needs only modest coverage. It adequately conveys the core effect but leaves behavior on missing or non-fillable nodes, reversibility, and partial fill types unaddressed.

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%, and the single parameter (nodeId) is documented in the schema as 'ID of the node'. The description adds no further meaning about the ID's expected format or accepted node types, so the baseline of 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?

The description states a specific verb and resource: 'Remove all fills of a node.' That is unambiguous and clearly a mutation of a single node's fill list. It stops short of naming a sibling it is distinct from (e.g., a fill-setting or style-applying tool), so it does not earn a 5.

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 tool versus alternatives such as setting a fill or applying a style. The description does not say whether the node must support fills, whether the operation is idempotent when there are no fills, or what happens to an already empty fill list.

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