Skip to main content
Glama
paragdesai1

Cursor Talk to Figma MCP

by paragdesai1

delete_multiple_nodes

Remove multiple design elements simultaneously from Figma by specifying node IDs, streamlining bulk deletion tasks in design workflows.

Instructions

Delete multiple nodes from Figma at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdsYesArray of node IDs to delete

Implementation Reference

  • The complete handler implementation for the 'delete_multiple_nodes' MCP tool. It registers the tool, defines its input schema (array of nodeIds), and provides the execution logic which forwards the command to the Figma plugin via sendCommandToFigma.
    // Delete Multiple Nodes Tool
    server.tool(
      "delete_multiple_nodes",
      "Delete multiple nodes from Figma at once",
      {
        nodeIds: z.array(z.string()).describe("Array of node IDs to delete"),
      },
      async ({ nodeIds }) => {
        try {
          const result = await sendCommandToFigma("delete_multiple_nodes", { nodeIds });
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error deleting multiple nodes: ${error instanceof Error ? error.message : String(error)
                  }`,
              },
            ],
          };
        }
      }
    );
  • Input schema for the delete_multiple_nodes tool requiring an array of node ID strings.
    {
      nodeIds: z.array(z.string()).describe("Array of node IDs to delete"),
    },
  • Registration of the delete_multiple_nodes tool using server.tool() in the MCP server.
    // Delete Multiple Nodes Tool
    server.tool(
      "delete_multiple_nodes",
      "Delete multiple nodes from Figma at once",
      {
        nodeIds: z.array(z.string()).describe("Array of node IDs to delete"),
      },
      async ({ nodeIds }) => {
        try {
          const result = await sendCommandToFigma("delete_multiple_nodes", { nodeIds });
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error deleting multiple nodes: ${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 for behavioral disclosure. It states this is a deletion operation (implying destructive behavior) but doesn't mention permissions required, whether deletions are permanent/reversible, rate limits, or what happens on partial failures. The description adds minimal behavioral context beyond the obvious destructive nature implied by 'delete'.

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 extremely concise - a single sentence that communicates the core functionality without any wasted words. It's front-loaded with the essential information ('Delete multiple nodes from Figma') and uses 'at once' to efficiently convey the batch nature. Every word earns its place in this minimal description.

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?

For a destructive mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context like error handling, permissions, whether the operation is atomic, what happens if some nodes don't exist, or what the return value might be. The combination of destructive operation + zero annotation coverage + no output schema requires more comprehensive description than provided.

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 single parameter 'nodeIds' clearly documented in the schema as 'Array of node IDs to delete'. The description doesn't add any parameter semantics beyond what the schema provides - it doesn't explain what node IDs are, where to get them, format requirements, or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 ('Delete multiple nodes') and resource ('from Figma'), making the purpose immediately understandable. It distinguishes from the sibling 'delete_node' by specifying 'multiple nodes at once', though it doesn't explicitly contrast with other deletion-related tools. The description avoids tautology by providing meaningful context beyond just the tool name.

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 'delete_node' for single deletions or other destructive operations. It lacks any mention of prerequisites, error conditions, or typical use cases. While the 'multiple nodes at once' phrasing implies a batch operation, there's no explicit comparison to sibling tools or context for decision-making.

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/paragdesai1/parag-Figma-MCP'

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