Skip to main content
Glama
the-real-talk

the-real-talk

get_node_info

Fetch detailed information about a specific Figma node at a chosen depth; returns partial results with a next cursor when the time budget expires.

Instructions

Get detailed information about a specific node in Figma, read from the live node down to the requested depth only (if the time budget is reached the answer says PARTIAL) (text nodes carry textStyle {id,name}; frames carry clipsContent). The subtree is limited by depth (default 1: the node and its direct children; deeper levels are replaced by childrenCount). Raise depth only when needed: a whole frame can be huge.

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": "get_node_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoLevels of children to return (default 1; 0 = the node alone)
nodeIdYesThe ID of the node to get information about
timeBudgetMsNoTime budget of the plugin for this call in ms (default 60000, max 100000). When it is reached the answer says it is PARTIAL and gives nextCursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: reads are live, results are depth-truncated with childrenCount replacing deeper levels, and a time budget can produce a PARTIAL answer. It also names payload specifics (textStyle on text nodes, clipsContent on frames). Gaps remain on failure modes (missing node IDs, permission/auth needs) and on what nextCursor looks like, which is only in the schema.

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?

One dense paragraph that front-loads the purpose, then nests caveats in parentheses. Every clause carries information, but the stacked parentheticals make it harder to scan than a short bulleted structure would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with no annotations and no output schema, the description does substantial work: it explains truncation, partial results, and payload shape specific to node types. Missing pieces are minor – explicit read-only assurance, error behavior, and the nextCursor contract are absent or left to the schema.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by explaining the consequence of depth ('deeper levels are replaced by childrenCount') and the cost tradeoff of raising it, plus the PARTIAL outcome tied to the time budget. That is genuine semantics, not a restatement of field descriptions, though it does not cover every edge case (e.g. depth 0 behavior appears only in the schema).

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 and resource: 'Get detailed information about a specific node in Figma, read from the live node down to the requested depth.' It is clearly distinguishable from a bulk lister like get_nodes_info through the singular 'a specific node', but it never names or contrasts any sibling, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Gives real guidance on one parameter ('Raise depth only when needed: a whole frame can be huge') and warns about cost, but offers no when-to-use/when-not-to-use framing against alternatives such as get_node_raw or get_nodes_info. Usage context is implied by the depth advice rather than explicit.

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

Deploy Server

Other Tools