Skip to main content
Glama

figma_set_fill

Sets a single-layer solid color fill on a Figma node, or removes the fill entirely with clear to make a frame truly transparent. Use it when rebuilding pixel-accurate layouts in the open Figma file.

Instructions

设置单层纯色填充,或用 clear 去掉填充(透明 Frame,不要用 a:0 冒充去底)。

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": "figma_set_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
fillNo
clearNo
nodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Because no annotations are provided, the description carries the full burden of explaining behavior. It does disclose that this is a mutation, that only one solid layer is supported, and that clear produces true transparency rather than alpha 0. It does not state whether existing fills are replaced or merged, what the tool returns, or what error conditions exist (for example, wrong node type or missing node), which are significant gaps for a write tool with zero annotation coverage.

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

Conciseness4/5

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

The definition is one tightly written sentence. The primary action is front-loaded, and the parenthetical serves as a concrete caution. The parenthetical adds useful weight, but it makes the sentence dense. Nothing is wasted.

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?

The tool has three parameters, a nested object, 0% schema coverage, no annotations, and no output schema, so the description must do more. It covers fill and clear semantics well and flags the alpha-0 pitfall. It does not cover the value ranges for the color channels, whether existing fills are overwritten, or nodeId expectations.

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 0%, so the description must carry parameter meaning. It explains fill as a single solid color and explains clear as removing the fill, including the alpha-0 pitfall. It does not mention the r/g/b numeric ranges or a's default value in the nested fill object, and it does not explain nodeId.

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: set a single-layer solid-color fill, or remove the fill with clear. The qualifier 'single-layer solid color' scopes it away from gradient, multi-layer, stroke, or effect tools, so the agent can tell it apart from figma_set_stroke or figma_set_effects. It does not explicitly name the node types it applies to, which is why it falls short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear guidance on parameter use: use clear instead of an alpha of 0 to make a Frame transparent, and says not to use alpha 0 to fake removing the background. However, the description gives no guidance on when to choose this tool over sibling tools such as figma_set_stroke or figma_update_node. That guidance is only implied by the tool's scope.

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