Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

batch_delete_nodes

Delete multiple scene nodes at once by passing a list of node paths, reducing repetitive removal calls in Godot projects.

Instructions

Delete multiple nodes from the scene in a single call.

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": {
      "node_paths": "<node_paths>"
    },
    "name": "batch_delete_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathsYesList of node paths to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden for a destructive operation. It never says deletions are irreversible or undoable, what happens to child nodes of deleted parents, or whether a missing path aborts the whole batch or is skipped — all critical for a bulk destructive call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with zero filler that states action and batching scope immediately. Its brevity is efficient rather than padded, though the space saved is not reused for missing behavioral detail.

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 batch tool with no annotations and no output schema, the definition says nothing about failure handling, partial application, or irreversibility. An agent can guess how to call it but cannot reason about consequences or error behavior, which is the main risk here.

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 a single parameter with 100% schema description coverage, so the schema already defines node_paths as a list of paths. The description only reinforces that the input is multiple nodes at once, adding no format, ordering, or validation semantics beyond the schema.

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?

"Delete multiple nodes from the scene in a single call" gives a specific verb (delete) and resource (nodes) plus the batch scope, which implicitly separates it from the singular delete_node sibling. It stops short of naming that sibling or stating any condition for choosing between them.

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?

"In a single call" implies the batch tool is preferred when several nodes must go, and the array parameter reinforces this. However, there is no explicit when-to-use guidance, no mention of the single-node alternative, and no stated preconditions such as editor mode or selection state.

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