Skip to main content
Glama

get_nodes_info

Retrieve detailed information about multiple Figma design elements by providing their node IDs for inspection and analysis.

Instructions

Get detailed information about multiple nodes in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdsYesArray of node IDs to get information about

Implementation Reference

  • Full implementation of the get_nodes_info MCP tool, including registration, input schema (nodeIds array), and handler logic that fetches node info for each ID via sendCommandToFigma and filters results.
    // Nodes Info Tool
    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)}`
              }
            ]
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation, potential rate limits, authentication needs, error conditions, or what 'detailed information' entails. The description is functional but lacks critical operational context.

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 that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, target, and context ('in Figma'), making it highly scannable and zero-waste.

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 and no output schema, the description is incomplete for a tool that presumably returns complex node data. It doesn't hint at the structure or content of the returned information, error handling, or limitations, leaving significant gaps for an AI agent to operate effectively.

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' clearly documented in the schema as an array of node IDs. The description adds no additional parameter semantics beyond what the schema provides, such as format examples, ID sourcing, or constraints, meeting the baseline for high schema coverage.

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 target resource ('multiple nodes in Figma'), making the purpose immediately understandable. It distinguishes from the sibling 'get_node_info' by specifying 'multiple nodes' versus presumably a single node, though it doesn't explicitly name the sibling for comparison.

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?

The description implies usage when needing detailed information about multiple nodes, but provides no explicit guidance on when to choose this over 'get_node_info' (e.g., batch efficiency vs. single-node specificity) or other sibling tools. It lacks context about prerequisites or exclusions.

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/agenisea/cc-fig-mcp'

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