Skip to main content
Glama

figma_get_node_tree

Read a Figma layout node tree by node ID to inspect page structure and child hierarchy, with an optional depth limit for focused browsing.

Instructions

读取 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_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
maxDepthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 disclosure burden, yet it only implies read-only behavior via '读取'. It says nothing about what the tree contains, whether the result can be very large, or how the maxDepth cap of 10 affects the returned volume.

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?

A single short clause with no wasted words and the resource front-loaded, but it is undersized rather than well-structured — there is essentially no second sentence to cover depth semantics or the return shape.

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 tree-traversal tool with no annotations, no output schema, and zero parameter documentation, the description is not complete enough for reliable invocation. An agent does not know the nodeId format, the maxDepth default, or what the returned tree looks like.

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% for both parameters, so the description must compensate and does not. Neither 'nodeId' (format, e.g. a Figma node key, and whether it accepts a page or frame id) nor 'maxDepth' (default value, and that 0 means a single level) is explained anywhere in the description.

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 names a verb ('读取') and a resource ('节点树'), so the basic operation is identifiable, but the qualifier 'layout 级' is unexplained and does not clearly separate this from the sibling figma_get_node (single node) or figma_get_document_info. An agent can guess it retrieves a subtree, but must infer the scoping distinction.

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?

'供浏览结构' implies a browsing/exploration use case but gives no when-to-use or when-not guidance and names no alternative. Nothing tells the agent to prefer figma_get_node for a single node or figma_get_document_info for the whole document.

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