figma-unlimited-mcp

Overview Schema Source Related Servers Discussions Admin

List nodes

list_nodes

Read-only

List nodes on a page or container, returning id, type, name, text, position, and size, to understand an existing board before editing.

Instructions

List nodes on the current page, or inside a specific container. Returns id, type, name, text, position and size for each. Use this to understand an existing board before editing it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_nodes"
  }
}

Input Schema

Name	Required	Description
`depth`	No	How many levels of children to include. 0 = direct children only.
`limit`	No	Maximum number of nodes to return.
`types`	No	Filter by node type, e.g. ["STICKY", "SHAPE_WITH_TEXT"].
`parentId`	No	Container to list. Defaults to the current page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotation readOnlyHint=true already covers safety. The description adds that the tool returns id, type, name, text, position, and size, and can operate on the current page or inside a container. This supplements the annotation with specific behavioral details without contradicting it.

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?

Three short sentences deliver purpose, return payload, and use case. There is no redundancy; each sentence is informative and front-loaded with the core action.

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

Completeness5/5

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

With 4 optional params and no output schema, the description explains return fields, scope, and intended use. It leverages the schema for parameter details, making it sufficiently complete for a read-only list operation. The use case is clear and aligned with the tool's role.

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 baseline is 3. The description mentions 'specific container' (mapping to parentId) but does not elaborate on depth, limit, or types. It adds marginal value beyond the schema, which already fully describes each parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'List nodes on the current page, or inside a specific container,' clearly identifying the action and scope. It lists return fields and the use case 'to understand an existing board before editing it,' which distinguishes it from sibling tools like find_nodes or get_node. This is a specific verb+resource with clear differentiation.

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

Usage Guidelines4/5

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

The description provides an explicit use case: 'Use this to understand an existing board before editing it.' This implies a read-only exploration context, but it does not explicitly state when not to use the tool or name alternative tools such as find_nodes for searching. Clear context with no exclusions or alternatives.

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