Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

get_nodes_info

Retrieve detailed information about multiple Figma design nodes by providing their IDs, enabling AI tools to access and analyze design elements for enhanced collaboration.

Instructions

Get detailed information about multiple nodes in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdsYesArray of node IDs to get information about

Implementation Reference

  • The handler function that implements the core logic of the get_nodes_info tool. It takes an array of nodeIds, fetches information for each using sendCommandToFigma('get_node_info'), filters the results with filterFigmaNode, and returns a formatted text response with the JSON data or an error message.
      async ({ nodeIds }) => {
        try {
          const results = await Promise.all(
            nodeIds.map(async (nodeId) => {
              const result = await sendCommandToFigma('get_node_info', { nodeId });
              return { nodeId, info: result };
            })
          );
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(results.map((result) => filterFigmaNode(result.info)))
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting nodes info: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Zod input schema for the get_nodes_info tool, defining the required 'nodeIds' parameter as an array of strings.
    {
      nodeIds: z.array(z.string()).describe("Array of node IDs to get information about")
    },
  • Registration of the 'get_nodes_info' tool on the MCP server using server.tool(), including the tool name, description, input schema, and inline handler function.
    server.tool(
      "get_nodes_info",
      "Get detailed information about multiple nodes in Figma",
      {
        nodeIds: z.array(z.string()).describe("Array of node IDs to get information about")
      },
      async ({ nodeIds }) => {
        try {
          const results = await Promise.all(
            nodeIds.map(async (nodeId) => {
              const result = await sendCommandToFigma('get_node_info', { nodeId });
              return { nodeId, info: result };
            })
          );
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(results.map((result) => filterFigmaNode(result.info)))
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting nodes info: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Higher-level registration call within registerTools() that invokes registerDocumentTools(server), which includes the get_nodes_info tool registration.
    registerDocumentTools(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets detailed information,' implying a read-only operation, but doesn't specify what information is returned (e.g., node properties, metadata), whether there are rate limits, authentication requirements, or error handling. For a tool with no annotation coverage, this leaves significant gaps.

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?

The description is a single, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given no annotations, no output schema, and a read operation with one parameter, the description is incomplete. It doesn't explain what 'detailed information' includes, potential constraints (e.g., max node IDs), or response format. For a tool in a rich ecosystem like Figma with many siblings, more context is needed to guide effective use.

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%, with the parameter 'nodeIds' fully documented in the schema as an array of node IDs. The description adds no additional semantic context beyond implying 'multiple nodes,' which is redundant with the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 the action ('Get detailed information') and resource ('about multiple nodes in Figma'), making the purpose immediately understandable. It distinguishes from the sibling tool 'get_node_info' by specifying 'multiple nodes' versus presumably a single node, though it doesn't explicitly name the alternative.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_node_info' (for single nodes) or 'get_document_info' (for broader document data). It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arinspunk/claude-talk-to-figma-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server