Skip to main content
Glama

delete_node

Remove a specific node from Figma designs using its ID to manage and update design elements programmatically.

Instructions

Delete a node from Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to delete

Implementation Reference

  • The complete MCP tool definition for 'delete_node', including registration with McpServer, input schema validation using Zod (nodeId: string), and the handler function that proxies the delete_node command to the underlying Figma plugin via WebSocket (sendCommandToFigma), with proper error handling and response formatting.
    server.tool(
      "delete_node",
      "Delete a node from Figma",
      {
        nodeId: z.string().describe("The ID of the node to delete"),
      },
      async ({ nodeId }) => {
        try {
          await sendCommandToFigma("delete_node", { nodeId });
          return {
            content: [
              {
                type: "text",
                text: `Deleted node with ID: ${nodeId}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error deleting node: ${error instanceof Error ? error.message : String(error)
                  }`,
              },
            ],
          };
        }
      }
    );
  • Zod input schema for the delete_node tool, requiring a single string parameter 'nodeId'.
    {
      nodeId: z.string().describe("The ID of the node to delete"),
    },
  • Registration of the 'delete_node' tool with the MCP server using server.tool(), specifying name, description, input schema, and handler.
    server.tool(
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. 'Delete' implies a destructive mutation, but it doesn't specify whether this is permanent, reversible, requires specific permissions, or has side effects on connected nodes. This is inadequate for a destructive operation.

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 wasted words. It's front-loaded with the core action and resource, making it immediately scannable and perfectly concise.

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 insufficient. It should address behavioral aspects like permanence, permissions, or error conditions, but provides only basic purpose without operational context.

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 'nodeId' well-documented in the schema. The description adds no additional parameter context beyond what the schema provides, so it meets 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 'Delete a node from Figma' clearly states the action (delete) and resource (node in Figma), making the purpose immediately understandable. However, it doesn't differentiate from sibling 'delete_multiple_nodes' which handles multiple deletions, so it's not a perfect 5.

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?

No guidance is provided about when to use this tool versus alternatives like 'delete_multiple_nodes' for bulk operations or other deletion-related tools. The description offers no context about prerequisites, permissions needed, or typical use cases.

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/pipethedev/Talk-to-Figma-MCP'

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