Skip to main content
Glama

figma_update_node

Updates a Figma node's name, position, size, visibility, opacity, rotation, and Auto Layout child sizing or absolute positioning using precise values.

Instructions

更新节点名称、位置、尺寸、可见性、透明度、旋转,以及 Auto Layout 子项的 FILL/HUG/绝对定位。

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_update_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNo
widthNo
heightNo
nodeIdYes
opacityNo
visibleNo
rotationNo
verticalSizingNo
horizontalSizingNo
layoutPositioningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden. It says 'update' but never states that unlisted properties are left untouched, whether the operation is atomic, what permissions/selection state are required, or what happens if nodeId is invalid or the node is locked. For a 12-parameter mutation tool this is a substantial gap.

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?

A single compact sentence that front-loads the verb and resource and groups related properties together. Nothing is redundant, though the property list dominates at the expense of any usage or behavioral context.

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 12 parameters, no annotations, and no output schema, so the description should do more. It covers the surface area of the parameters but omits partial-update semantics, units/coordinate space, enum meaning, and failure behavior — leaving real ambiguity for an agent calling it.

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 compensate. It does map its listed concepts onto most parameters (name, x/y as 位置, width/height as 尺寸, visible, opacity, rotation, horizontalSizing/verticalSizing and layoutPositioning as Auto Layout 子项 FILL/HUG/绝对定位). But it gives no units, coordinate space, value ranges, or explanation of FIXED/HUG/FILL and AUTO/ABSOLUTE semantics, so the three enums remain unexplained.

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?

States a specific verb (更新/update) and resource (节点/node) and enumerates the mutable property groups: name, position, size, visibility, opacity, rotation, and Auto Layout child sizing/positioning. An agent can tell this is the general-purpose node mutator. It does not, however, distinguish itself from overlapping siblings such as figma_move_node (x/y) or figma_set_auto_layout.

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 when-to-use or when-not-to-use guidance at all. Given siblings that overlap on the same properties (figma_move_node for position, figma_set_auto_layout for layout behavior), the definition never says which tool should be preferred for those cases.

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