video-workflow

ArcReel Video Workflow

Use the connected ArcReel MCP service as the sole source of project state. Every project-level tool call must explicitly specify the project and must not rely on local project files or the Agent host's working directory.

Route by plan

1. Use ArcReel project tools to determine the project. When there is no project yet, first gather the information needed for creation and create the project.
2. For that project, call get_workflow_plan. Pass episode only when the user has already selected an episode. Preserve any still-valid temporary selections returned or required by the plan.
3. When the user only asks to check progress or learn the next step, report the steps, issues, and next_actionin the plan without modifying the project.
4. When the user asks to advance, route and execute that action based solely on workflow_plan.next_action ; pass project,next_action.args, target fields, and non-empty requested_ids。
5. to the corresponding ArcReel tool as needed. When an action requires the user to choose or confirm, explain the impact and wait for explicit consent.next_action.type When it is none , show the blocking reason and stop modifying the project; when it is export , explain that the workflow is ready and hand off to the WebUI or embedded host, because the remote MCP is not responsible for compositing or exporting the final video.
6. When a generation action returns generation_batch , preserve batch_id, and follow each returned poll_after_seconds to call get_generation_batch, until the result is done: true. After that, call get_workflow_planand route according to the new next_action . When the plan returns wait_for_task because a task already exists, wait for its poll_after_seconds and then call get_workflow_planagain, for at most max_poll_attempts times; if the same task is still running after reaching the limit, report its task_ids and stop. After other actions complete, refresh the plan directly.

Read the corresponding reference only when the topic applies:

• When encountering blocking, temporary selections, billable actions, or stale artifacts, readPlan Safety and Confirmation。
• When explaining the structure or references of different modes, readContent and Generation Modes。
• When selecting IDs, or reporting batch results, tasks, provider submissions, and artifact status, readGeneration Results。