Skip to main content
Glama

figma_get_node

Read a single Figma node and return its summary, layout, or rest JSON at a chosen depth to inspect structure or support pixel-level reconstruction.

Instructions

读取单个节点。detail=summary|layout|rest_json,默认 layout。

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

Input Schema

NameRequiredDescriptionDefault
detailNo
nodeIdYes
maxDepthNo

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?

No annotations are supplied, so the description carries the full burden. '读取' implies a read-only operation, but there is nothing about auth/plugin connection requirements, whether the call is cheap or expensive, or how detail=rest_json differs behaviorally (payload size, latency, failure modes) from summary/layout.

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?

Two terse sentences with no filler, and the detail options are front-loaded. It is efficient, though the terseness shades into under-specification rather than being a model of concision.

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?

With no output schema and no annotations, the description should explain what each detail level returns, since detail is the main control knob on response shape and size. It gives the enum and default but not the consequence of choosing one level over another, leaving a meaningful gap for a 3-parameter read tool.

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%, so the description must compensate, and it only partially does: it lists the detail enum values and supplies the default (layout), which the schema itself does not declare. nodeId and maxDepth — including the 0-10 depth cap and what depth actually limits — are left entirely unexplained.

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 verb+resource (读取/read a single node) is clear, and the 'single' qualifier weakly hints at the boundary with figma_get_node_tree. However, it never names or distinguishes itself from that sibling or from figma_read_for_implement, so the agent must infer the split from the names alone.

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?

The only guidance is the default value of detail (layout). There is no statement of when to use this tool versus figma_get_node_tree or figma_read_for_implement, and no prerequisites such as needing a valid nodeId or current page context.

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