Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

delete_node

Remove a specific node from the Figma canvas by providing its node ID, decluttering your design.

Instructions

Remove a node from the canvas.

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": "delete_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesNode ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

B3.1/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 the full burden of behavioral disclosure. It states that a node is removed but does not mention that the operation is destructive/irreversible, what happens to child nodes, or any safety concerns. For a deletion tool, this is a meaningful gap.

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, focused sentence that immediately states the action and target. It is concise without unnecessary elaboration, and every word earns its place.

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 one-parameter deletion tool, the description is minimally adequate. However, with no annotations and no output schema, it would benefit from noting irreversibility or side effects on connected nodes. The lack of such context leaves gaps but does not make the tool unusable.

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%, and the nodeId parameter is already documented as 'Node ID to delete'. The description adds no additional parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb ('Remove') and a clear resource ('a node from the canvas'). It clearly conveys the tool's operation, though it does not explicitly differentiate itself from related siblings such as batch_delete or delete_page.

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?

There is no guidance on when to use delete_node versus alternatives like batch_delete or delete_page. No context, prerequisites, or exclusion criteria are provided, leaving the agent to infer the appropriate usage scenario.

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

Deploy Server

Other Tools