BeatBandit MCP

Tools

/

Shot / Media / Export

/

shot_list_generate

shot_list_generate

orchestration
beta
auth: project:write
approval: suggest
status: v1

Run BeatBandit's backend-owned shot-list generation workflow for a project, scene, or episode scope. Start it once, then follow progress through `job_get`.

When to use

Use when the user wants BeatBandit to generate or regenerate a shot-list scope.

Use when the caller wants BeatBandit to own the full shot-list generation lifecycle instead of manually driving pass-by-pass finalize steps.

Use `shot_mode` as clip length / grouped generation length, not as the duration of each individual camera cut.

For modern storyboard-to-video workflows, use the default `shot_mode=length_15`, `shot_split_mode=hidden`, and `shot_field_preset=seedance_storyboard` unless the user explicitly asks for different clip lengths or formatting.

After the job completes, strongly prefer this visual-reference order unless the user explicitly skips it: query assets, create or select a Scene Moodboard with `image_generate(workflow=generate_scene_moodboard)`, then create recurring reference images with `image_generate(workflow=generate_element)` using that moodboard as a reference source when possible, and only then generate per-shot storyboard frames. If the scene is simple, skip the recurring reference images step, create just the scene moodboard and use it as the common reference source for all the shots in the scene (since it describes the key visual elements of the scene).

When not to use

Do not use for manual shot CRUD after a scope already exists.

Do not use for image, video, or media generation.

Examples

“Generate a shot list for scene 50.10.20.”

“Check whether this project is ready for shot-list generation before starting a scoped run.”

“Start the default storyboard-to-video shot list with `payload={"scope_type":"project","shot_mode":"length_15","shot_split_mode":"hidden","shot_field_preset":"seedance_storyboard","also_create_compact_video_prompt":true,"auto_manage_timeline":true}`.”

“Once the completed job is returned by `job_get`, inspect `shot_list_query(mode=assets)`, generate/select a Scene Moodboard, then generate recurring element references before shot frames.”

Anti-examples

  • List shots already in the scope.
  • Jump straight from a completed shot-list job to per-shot `image_generate(workflow=generate_shot)` calls when no Scene Moodboard or recurring reference images exist; generate/select the moodboard and recurring references first unless the user explicitly says to skip them.

Workflows

Switch behavior by setting the workflow input field.

generate_scope

readiness
start
Calls: shot_list.generate

Linked resources

Tool calls may return resource_links pointing at these resource families.

shot_list_scope

Input schema

shot_list_generate input
{
  "$ref": "./shot_list.generate.input.json"
}

Output schema

shot_list_generate output
{
  "$ref": "./shot_list.generate.output.json"
}

← All toolsv1 · workflow_runner