Skip to main content
Glama

figma_set_stroke

Sets a single solid stroke on a Figma node by specifying its ID, color, and weight, enabling precise border styling during canvas edits.

Instructions

设置单层实线描边。

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>",
      "color": "<color>",
      "weight": "<weight>"
    },
    "name": "figma_set_stroke"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes
nodeIdYes
weightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description bears full behavioral burden, yet it only implies a mutation. It does not disclose whether existing strokes are replaced or appended, what permissions or node types are required, what happens to multi-layer strokes, or what the result is.

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?

The single sentence is front-loaded and free of padding, but its brevity reflects under-specification rather than efficient communication of the information an agent needs.

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?

For a three-parameter mutation tool with a nested object, no annotations, and no output schema, the description leaves nearly all call-critical information (target node, overwrite behavior, color format) unstated.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds nothing about the three required parameters, including the nested color object with r/g/b/a and the numeric weight. An agent must infer nodeId, color, and weight semantics entirely from the raw schema.

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 a concrete verb and resource ('设置...描边' / set stroke) and narrows it to a single-layer solid stroke, which distinguishes it from figma_set_fill or figma_set_effects at a glance. However, it never says what object the stroke is applied to (a node, by implication only), so the purpose is only partially pinned down.

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

Usage Guidelines1/5

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

There is no guidance at all on when to use this tool versus alternatives such as figma_set_fill, or on prerequisites like having a selected node. The single sentence offers no usage context or exclusions.

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