Squall MCP Workflow Examples
These examples use the workflows supported by the current MCP server. Project creation, script generation, script approval, and episode restructuring still happen in the web app; MCP takes over once there is project state for an agent to inspect and operate on.
Produce Media for an Existing Microdrama
- 1
list_projectsFind the Squall project by title and confirm the account owns it.
- 2
get_project_episodesChoose the episode that is ready for shot generation.
- 3
get_episode_editorLoad the episode tree, including shots, characters, looks, locations, and jobs.
- 4
generate_character_imageGenerate missing character reference images when the project still needs them.
- 5
generate_location_imageGenerate location reference images for approved location records.
- 6
generate_shot_background_imageGenerate empty plates for short shots that need location-specific backgrounds.
- 7
generate_shot_clipStart the video generation job for the planned shot.
- 8
get_jobPoll the returned job id until it succeeds or fails.
Review and Tighten a Scene
- 1
list_projectsFind the project the user named.
- 2
get_project_episodesResolve the requested episode by number or title.
- 3
get_scene_assetsRead the scene, including shots, referenced characters, locations, and continuity assets.
- 4
update_shotPatch only the changed shot fields. Dialogue changes must target camera_setup.short_shots[].dialogue_covered.
- 5
get_episode_shotsRead the shots again and summarize exactly what changed.
Adjust a Shared Location Safely
- 1
get_project_locationsFind the location and inspect where it appears before changing it.
- 2
get_locationRead the current location fields and decide whether the change belongs to the shared record.
- 3
update_locationPatch only the changed fields. Text and prompt edits mark the location image stale.
- 4
get_scene_assetsReview scenes that use the location so the user understands the downstream effect.
Current Creation Boundary
generate_script covers the empty state: it writes a script into a new project, and seeds that project's characters, locations, episodes and shots along with it. Importing an existing script, approving one, and restructuring episodes are not exposed by the current MCP registry, so those steps still happen in the web app.
