Skip to main content
Glama

figma_move_node

Move a Figma node to specific X/Y coordinates and optionally reassign its parent to adjust canvas layout.

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>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "figma_move_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
indexNo
nodeIdYes
parentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say whether x/y are absolute or parent-relative, what happens to the node's index or children when reparenting, whether the operation is reversible, or what permissions are needed. For a mutation tool this is a significant gap.

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 waste, but its brevity comes at the cost of under-specification rather than genuine efficiency. It is concise without being informative.

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?

A 5-parameter mutation tool with no annotations, no output schema, and 0% schema coverage needs a much richer description to be callable correctly. Key details such as coordinate reference frame, index behavior, and reparenting side effects are missing.

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?

Schema description coverage is 0% across 5 parameters, and the description only implicitly covers nodeId and parentId. The required x, y coordinates and the optional index parameter are left entirely unexplained, so an agent cannot know their semantics or coordinate space.

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 names a specific verb (移动/move) and resource (节点/node) and adds the optional reparenting capability, which distinguishes it from generic update tools. It does not explicitly contrast with siblings like figma_update_node, keeping it short of 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 figma_update_node or the create_* tools, and no prerequisites or exclusions are stated. The only usage signal is the implied 'move a node' from the name and description.

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