Skip to main content
Glama
andreycretsu

Cursor Talk to Figma MCP

by andreycretsu

delete_multiple_nodes

Remove multiple design elements simultaneously from Figma files to streamline cleanup and organization tasks.

Instructions

Delete multiple nodes from Figma at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdsYesArray of node IDs to delete

Implementation Reference

  • The handler function that executes the 'delete_multiple_nodes' MCP tool. It proxies the call to the Figma plugin by sending a 'delete_multiple_nodes' command with the provided nodeIds via sendCommandToFigma, then returns the result as content or an error message.
    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)
                  }`,
              },
            ],
          };
        }
      }
    );
  • The input schema for the 'delete_multiple_nodes' tool using Zod: an array of node ID strings.
    {
      nodeIds: z.array(z.string()).describe("Array of node IDs to delete"),
    },
  • The registration of the 'delete_multiple_nodes' tool on the MCP server using server.tool(), including name, description, schema, and handler.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Delete multiple nodes from Figma at once', which implies a destructive mutation, but doesn't address critical aspects like permissions required, whether deletions are permanent or reversible, error handling for invalid node IDs, or rate limits. For a destructive tool with zero annotation coverage, this is a significant gap in behavioral 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 with zero waste: 'Delete multiple nodes from Figma at once'. It is front-loaded with the core action and resource, making it immediately understandable. Every word earns its place, and there is no redundant or verbose language.

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 the tool's destructive nature, lack of annotations, and absence of an output schema, the description is incomplete. It doesn't cover behavioral traits like permanence, permissions, or error handling, nor does it explain return values or side effects. For a mutation tool with no structured safety hints, the description should provide more context to ensure safe and correct usage.

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?

The input schema has 100% description coverage, with the parameter 'nodeIds' clearly documented as 'Array of node IDs to delete'. The description adds no additional semantic context beyond what the schema provides, such as format examples or constraints on node ID validity. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 verb ('Delete') and resource ('multiple nodes from Figma'), making the purpose unambiguous. It distinguishes from the sibling 'delete_node' by specifying 'multiple nodes at once', though it doesn't explicitly name the alternative. The description is specific but could be more explicit about the sibling differentiation.

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'. It mentions 'multiple nodes at once', which implies a batch operation, but doesn't specify thresholds or scenarios where batch deletion is preferred over individual deletion. No exclusions, prerequisites, or explicit alternatives are provided.

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/andreycretsu/cursor-talk-to-figma-mcp-main'

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