Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

delete_node

Remove a specific element from Figma designs by providing its node ID to clean up and modify layouts.

Instructions

Delete a node from Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to delete

Implementation Reference

  • The async handler function for the 'delete_node' MCP tool. It sends a 'delete_node' command to Figma via sendCommandToFigma with the nodeId and returns a success or error text response.
    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 'nodeId' string.
      nodeId: z.string().describe("The ID of the node to delete"),
    },
    async ({ nodeId }) => {
  • Registration of the 'delete_node' tool on the MCP server using server.tool(), providing name, description, input schema, and handler.
      "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)}`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this operation is reversible, what permissions are required, what happens to child nodes, or whether there are confirmation prompts. For a destructive tool with zero annotation coverage, this is inadequate.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple destructive operation and front-loads the essential information.

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 doesn't explain what 'delete' means in this context (permanent removal? moves to trash?), what the response looks like, error conditions, or important behavioral aspects. The combination of destructive nature and lack of structured metadata requires more descriptive 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' fully documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema, so it meets the baseline expectation but doesn't provide extra value.

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') and target resource ('a node from Figma'), providing a specific verb+resource combination. However, it doesn't differentiate this destructive operation from similar sibling tools like 'ungroup_nodes' or 'flatten_node' that might also remove or transform nodes in different ways.

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. With siblings like 'ungroup_nodes' (which disassembles groups) and 'flatten_node' (which merges layers), there's no indication of when deletion is appropriate versus other node-removal operations, nor any mention of prerequisites or consequences.

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