Skip to main content
Glama

figma_delete_node

Deletes a specified node from the currently open Figma file by node ID; use it to remove canvas elements while protecting PAGE and DOCUMENT nodes from deletion.

Instructions

删除节点。不能删除 PAGE 或 DOCUMENT。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nodeId": "<nodeId>"
    },
    "name": "figma_delete_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It discloses one meaningful constraint (PAGE and DOCUMENT nodes cannot be deleted), but says nothing about whether deletion is recursive for child nodes, whether it is reversible/undoable, or what permissions are needed for a destructive mutation.

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?

Two short sentences, action first and constraint second, with zero filler. It is appropriately sized for a one-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter destructive tool with no output schema, the description covers what it does and the key type restriction. It is still thin on the consequences of a delete (cascading children, reversibility) that an agent needs before invoking an irreversible mutation.

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?

There is only one parameter, nodeId, with 0% schema description coverage, so the description is the only source of meaning. It implies the parameter identifies the node to delete but adds no format, source, or example beyond that implication.

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 states a specific verb and resource (delete a node) and immediately narrows the domain by excluding PAGE and DOCUMENT node types. An agent can distinguish this from figma_move_node or figma_update_node, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is an implicit usage boundary via the exclusion of PAGE and DOCUMENT, which tells the agent when the call will fail. However, there is no guidance on when to prefer this over alternatives, no prerequisites, and no note about how to obtain a valid nodeId.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.