Parallel tool calls: fan out Sume renders, wait once

The ElevenLabs changelog for Sep 21, 2026 says ElevenAgents can execute multiple tools in one turn when parallel tool execution is enabled. On Sume's hosted MCP the matching pattern is to submit several jobs, then call jobs_wait once with job_ids (1 to 20) and wait_for set to all or any.

Why one batch wait

Parallel tool calls cut the number of agent turns, but each paid create still needs its own idempotency_key. The slow part of media work is rendering, not the call, so the useful step is waiting on the whole batch at once instead of one id at a time.

What jobs_wait does with many ids

Sume's batch wait returns a status snapshot for every requested id.

Handling long renders

A wait that hits its slice returns wait_slice_expired. Call jobs_wait again with the same ids. Never resubmit the paid create, since the original jobs are still running and still bill.

If a render runs for minutes, repeat the wait rather than asking for a longer timeout; larger values are clamped and the response says so.

When to use script_run instead

For three or more independent calls of the same shape, the docs recommend script_run, which runs a short JavaScript program on the Sume side, can call tools in parallel, and returns the child jobs[] to wait on. Paid creates inside it still need their own idempotency_key.

Arguments for one batch wait over three submitted jobs:

{
  "job_ids": ["job_a", "job_b", "job_c"],
  "wait_for": "all",
  "include_results": true
}