Skip to main content
Glama
the-real-talk

the-real-talk

set_paints

Replace a node's fills or strokes with solid paints—optionally bound to COLOR variables—or gradients to apply consistent styling in Figma.

Instructions

Replace the fills or strokes of a node with solid paints (optionally bound to COLOR variables) and/or gradients. Images: use set_image_fill.

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>",
      "target": "<target>",
      "paints": "<paints>"
    },
    "name": "set_paints"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
paintsYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully frames the operation as a full replacement of existing paints rather than an append, and mentions variable binding and gradient support, but says nothing about permissions, error behavior, the 8-paint cap, or whether the node is created/validated.

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?

Two short sentences, front-loaded with the action and payload, then the escape hatch to the sibling. No filler or redundancy.

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?

For a mutation tool with no annotations and no output schema, the definition covers what it does and the image alternative but leaves out return values, failure modes, and the replacement/ordering semantics of the paints array. Adequate to start a call, not complete enough to predict its effects.

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?

Reported schema description coverage is 0% at the top level, so the description must compensate; it only really explains that paints may be solid, variable-bound, or gradient. It adds nothing about nodeId, the fills/strokes target semantics, paint ordering/stacking, or the maxItems limit, leaving deeper schema knowledge as the only source.

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?

A specific verb ("Replace") plus resource ("fills or strokes of a node") plus the payload types (solid paints, COLOR-variable-bound, gradients). It also names the sibling set_image_fill as the tool for images, so an agent can distinguish the two without opening schemas.

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?

Gives an explicit exclusion ("Images: use set_image_fill"), which is real routing guidance. However it never addresses when to prefer this over the sibling color setters (set_fill_color / set_stroke_color) that seemingly do a narrower version of the same job.

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