Godot AI

Overview Schema Source Related Servers Discussions Admin

Batch Execute

batch_execute

Execute multiple Godot editor sub-commands sequentially, stopping on first error. Automatically rolls back successful steps if any later command fails, enabling safe multi-step scene edits.

Instructions

Execute a list of editor sub-commands in order, stopping on first error.

Each item must be {"command": "<plugin_command>", "params": {...}}. Use the underlying plugin command names (e.g. create_node, set_property, delete_node, attach_script), not the MCP tool names. Commands run sequentially; execution stops at the first error. When undo is True (default), any successful sub-commands are rolled back via the scene's undo history if a later sub-command fails, producing atomic-on-failure semantics.

Use this to compose multi-step edits (create node + set property + attach script) into a single tool call. Rollback works for sub-commands that modify the currently edited scene. batch_execute itself is not allowed as a sub-command.

Scene paths are relative to the edited scene root (e.g. "/Main/Enemy"), NOT runtime "/root/..." paths. The example below assumes the scene root is named "Main" — substitute the actual root name.

Input Schema

TableJSON Schema

Name	Required	Description
`undo`	No	Roll back succeeded sub-commands on failure. Default True.
`commands`	Yes	List of `{"command": str, "params": dict}` items.
`session_id`	No	Optional Godot session to target. Empty = active session.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.1.4Aug 10, 2026
Removedv3.0.7Jul 26, 2026
First observedv2.9.1Jul 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries full behavioral disclosure and does so thoroughly: sequential execution, stop-on-first-error, undo rollback semantics with atomic-on-failure, path conventions relative to scene root, and the prohibition on nested batch_execute. This is exactly the behavioral information an agent needs beyond the schema.

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?

The description is front-loaded with the core purpose and each paragraph adds necessary detail without padding. It loses one point because it references 'the example below' but no example is actually present, which is a structural inconsistency.

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

Completeness4/5

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

Given the tool's high complexity and the presence of an output schema, the description covers command format, failure semantics, rollback, and path conventions almost completely. The missing literal example is the only notable gap, and the explicit statement of an absent example is a small but real completeness defect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds real value by defining the exact shape of each commands item, mandating plugin command names rather than MCP tool names, and clarifying scene-path semantics, which are not apparent from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

First sentence gives a precise verb and resource: execute a list of editor sub-commands in order, stopping on first error. It also clarifies the distinction from MCP tool names and frames the tool as a multi-step composition, which separates it from the many single-operation sibling tools.

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

Usage Guidelines4/5

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

The description explicitly says to use this for composing multi-step edits into one call, such as create node + set property + attach script. It does not explicitly name single-step alternatives or state when not to use it, but the composition guidance is clear enough for an agent to route correctly.

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