Skip to main content
Glama

delete_node

Remove design elements from Figma by specifying their node ID to manage and clean up your workspace.

Instructions

Delete a node from Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to delete

Implementation Reference

  • The core handler function for the 'delete_node' MCP tool. It sends a 'delete_node' command to the Figma plugin via websocket with the provided 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)}`,
            },
          ],
        };
      }
    }
  • Registers the 'delete_node' tool on the MCP server using server.tool(). Includes tool name, description, input schema (nodeId), and references the handler function. This function is called from tools/index.ts.
    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 schema for 'delete_node' tool input validation: requires a single 'nodeId' string parameter.
    {
      nodeId: z.string().describe("The ID of the node to delete"),
    },
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 the action ('Delete') but doesn't explain what 'delete' entails—whether it's permanent, reversible, requires specific permissions, affects child nodes, or has rate limits. This leaves significant gaps 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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse at a glance.

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 tool with no annotations and no output schema, the description is inadequate. It doesn't cover behavioral aspects like permanence, permissions, or error cases, nor does it explain return values or side effects. Given the complexity of deletion in a design tool, more context is needed.

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 'nodeId' clearly documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as format examples or constraints. This 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 clearly states the verb ('Delete') and resource ('a node from Figma'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'ungroup_nodes' or 'flatten_node' which 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. For example, it doesn't clarify if this is for permanent deletion versus other node-removal operations, or mention prerequisites like needing node permissions. No explicit when/when-not statements or sibling comparisons are included.

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