Skip to main content
Glama

Execute canonical action batch

execute_batch
Destructive

Executes ordered scene actions and read operations in one atomic round-trip, applying safety checks, timeline reconciliation, and layout fixes before committing updates to a project.

Instructions

Execute an ordered array of canonical actions (and/or read tools) in a single atomic round-trip without autonomous_edit. Automatically runs safe-zone checks, timeline reconciliation, layout de-stacking, async asset completion, and commits the updated scene to project_id.

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": {
      "actions": "<actions>"
    },
    "name": "execute_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneNoOptional inline scene.
assetsNoOptional media assets to seed a new project.
actionsYesOrdered list of { action, params } steps to execute.
video_urlNoOptional source video URL to seed a new project.
project_idNoProject id for state persistence across calls.
include_sceneNoIf true, include the full raw scene JSON in the response (omitted by default in favor of liveLayers).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false, destructiveHint=true and openWorldHint=true, and the description adds real substance beyond them: safe-zone checks, timeline reconciliation, layout de-stacking, async asset completion, and a scene commit to project_id. It does not spell out rollback/error semantics if one action fails mid-batch or the cost of the commit, which keeps it short of a 5.

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?

A single sentence front-loads the core operation before enumerating the automatic steps, with no filler. The trailing list of automatic behaviors is a long run-on clause that could be split for readability.

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 destructive, open-world batch executor with a nested free-form actions array, the description covers side effects but omits how to discover valid action names and params (the get_action_schema sibling exists for this) and says nothing about failure behavior. Adequate but with clear gaps for a tool of this complexity.

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%, so the baseline is 3. The description reinforces that 'actions' is an ordered list and that project_id carries state across calls, but the schema already states persistence, and it adds nothing about valid action names or params shape for the nested objects.

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 and resource ('Execute an ordered array of canonical actions') and adds scope detail ('single atomic round-trip', 'commits the updated scene to project_id'). It explicitly excludes autonomous_edit, but never contrasts with the closest sibling execute_action, leaving the single-vs-batch distinction for the agent to infer.

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?

It gives an implied usage context (batch of ordered actions, with or without read tools) and one exclusion (without autonomous_edit), but no explicit 'use X when' routing such as 'call execute_action for one action' or 'use queue_edit for background jobs'. Guidance must be inferred from siblings the description never names.

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