Claude Opus 5.5 programmatic tool calling: when video jobs fit it

Opus 5.5 supports programmatic tool calling. Fan-out video jobs fit it, sequential renders do not. Which Sume calls batch well and which stay one by one.

4 min readSume
All posts

Claude Opus 5.5 is on Anthropic's list of models that support programmatic tool calling, along with Opus 5, Sonnet 5.5 and Fable 5.1, according to the docs read on 2026-10-04. Haiku 4.5 accepts the tool version but does not support the feature. For a video workflow, the useful question is which calls batch well, because the same page says the feature fits fan-out across many items and fits poorly for strictly sequential steps or a few small calls.

Which video calls are fan-out?

Sume's script_run tool description names the shape it is for: three or more independent calls of the same shape in one turn, such as a tts_create per sentence, a generate_image per scene, video_frames_create at many timestamps, or jobs_wait then jobs_result over a wave of jobs. Those items do not depend on each other, so a loop is the natural form.

Two or fewer calls should be made directly. The same description says to call them directly rather than script them.

Which stay sequential?

A talking-head shot is a chain. Sume's avatar tool notes describe it as a still, then tts_create, then an avatar image-to-video call on that still. Each step needs the previous output, so a loop adds nothing. Treat each chain as one unit and fan out across shots, not within a shot.

Rendering is the other limit. A script run is bounded by timeout_seconds (5 to 55, default 45), so it should submit creates and return job ids, then jobs_wait outside it. The Jobs and results page covers polling and results.

A decision table

Fit judged from Anthropic's programmatic tool calling page and Sume's tool descriptions, both read 2026-10-04.
TaskShapeRoute
10 scene stillsindependent, same toolone script_run with 10 generate_image creates
One voice linesingle callcall tts_create directly
Talking-head shotchain of 3 stepsdirect calls in order
Check 20 finished jobsindependent readsjobs_wait with up to 20 ids
Frames at 8 timestampsindependent, same toolscript_run with video_frames_create

What about cost and tokens?

Anthropic suggests measuring billed input tokens with and without allowed_callers before assuming a saving, and Sume's guidance is similar in spirit: the bound is per run. A script run defaults to 32 calls and 16 paid calls, with ceilings of 64 and 32, and every paid create needs its own idempotency_key.

Set max_spend_usd on paid calls if you want a hard ceiling, because Sume enforces it only when you send it. A dry_run previews admission and cost without submitting. See MCP tools and gates for the gate list.

Sources

Related posts

More in Agents

All Agents posts

Written by Sume