@echobt/figma-mcp

Overview Schema Source Related Servers Discussions Admin

get_node_by_id

Retrieve detailed information about a specific node in a Figma file using its GUID, including layout, styles, effects, and children up to 10 levels deep.

Instructions

Get detailed information about a specific node by its GUID. Node ID format: 'sessionID:localID' (e.g., '457:1607'). Hyphen format also accepted.

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": {
      "filePath": "<filePath>",
      "nodeId": "<nodeId>"
    },
    "name": "get_node_by_id"
  }
}

Input Schema

Name	Required	Description
`nodeId`	Yes	GUID string in format 'sessionID:localID' (e.g., '457:1607') or 'sessionID-localID'
`compact`	No	Use compact JSON formatting (no indentation) (default: false)
`filePath`	Yes	Path to the .fig file
`maxDepth`	No	Maximum depth to traverse children (default: 1, max: 10)
`includeLayout`	No	Include layout inference (gap, padding, alignment) (default: true)
`includeStyles`	No	Include style properties (fills, strokes, effects) (default: true)
`includeEffects`	No	Include effects (shadows, blurs) (default: true)
`includeChildren`	No	Include child nodes in response (default: true)
`includeImageRefs`	No	Include image reference metadata (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Jul 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It mentions returning 'detailed information' but does not disclose any side effects, permissions, or limitations (e.g., whether it's read-only). The mention of various include flags implies it can filter output, but that is already in the schema. Overall, minimal behavioral disclosure beyond the literal action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences effectively front-load the purpose and key detail (ID format). No wasted words.

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 9 parameters and no output schema, the description is minimal. It covers the core purpose but does not explain the return structure or when to use specific parameters. For a tool with many customizable flags, more context would be helpful, though the schema does describe each parameter.

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. The description adds value by explaining the node ID format and that hyphen format is also accepted. This helps the agent understand parameter syntax beyond the schema description.

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 clearly states 'Get detailed information about a specific node by its GUID' and provides the ID format. It is specific about the resource (node) and action (get detailed info), though it does not explicitly distinguish it from sibling tools like get_node_details.

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?

No guidance is given on when to use this tool versus alternatives like find_nodes or get_node_details. The description lacks context for selection among many sibling tools.

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