Batch Run
batch_runRuns multiple domain-tool calls in one ordered server-side request, stopping at the first failed or unverified step and reporting every outcome; steps can reference earlier results via templates.
Instructions
Run several domain-tool calls in ONE call, in order, server-side.
Prefer it whenever the next calls are known: e.g. set metadata and color on four clips, add markers, rename tracks. Each step is {tool, op} exactly as you would call that tool, and is validated, verified and audited the same way. A step's op may read an earlier step's output with a template: "{{ steps..receipt.result.id }}" (writes), "{{ steps..result... }}" (reads), [n] and [*] supported. Stops at the first failed or unverified step; every outcome is reported. With *_delete steps the first call returns a plan + confirm_token for the whole batch.
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": {
"steps": "<steps>"
},
"name": "batch_run"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| steps | Yes | Steps, in order. | |
| dry_run | No | Plan only. | |
| verbose | No | Full receipts for every step. | |
| confirm_token | No | When it contains *_delete steps: token from the plan. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| plan | No | ||
| steps | No | ||
| recipe | Yes | ||
| status | Yes | ||
| outputs | No | ||
| duration_ms | No |