Skip to main content
Glama
the-real-talk

the-real-talk

get_nodes_info

Retrieve detailed information for multiple Figma nodes, including child levels by depth and partial results with cursors when a time budget is reached. Use it to inspect node structure and properties.

Instructions

Get detailed information about multiple nodes in Figma

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": {
      "nodeIds": "<nodeIds>"
    },
    "name": "get_nodes_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoLevels of children to return for each node (default 1)
nodeIdsYesArray of node IDs 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

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it only implies a read via "Get". It never mentions that responses can be PARTIAL with a nextCursor when the plugin time budget is exhausted, nor any permission or size constraints — behaviorally important for a multi-node fetch.

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 front-loaded sentence with zero filler. It is efficient, though the terseness leaves the gaps noted in other dimensions rather than being padded or disorganized.

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?

With no annotations and no output schema, the description should explain what "detailed information" includes and how partial results behave. For a multi-node retrieval tool with a depth parameter and a time-budget mechanism, a single sentence is insufficient.

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 100%, so nodeIds, depth, and timeBudgetMs (including the PARTIAL/nextCursor note) are fully documented in the schema. The description adds no meaning beyond it, which is the baseline expectation here.

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 multiple nodes"), and the word "multiple" implicitly distinguishes it from the singular get_node_info sibling. It does not explicitly name that sibling, but an agent can still tell what this tool returns.

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?

Batch usage is only implied by "multiple nodes"; there is no explicit statement of when to prefer this over get_node_info or get_node_raw, and no prerequisites or limits are given. The intent is inferable but not stated.

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