job_get
Read normalized async job state, progress, and related resource links. This is the canonical follow-up surface for long-running BeatBandit workflows such as `story_bootstrap`, `screenplay_import_run`, and MCP-owned `screenplay_writer`.
When to use
Use when a previously started BeatBandit job needs progress or result inspection.
Use this to follow backend-owned workflows such as `story_bootstrap`, `screenplay_import_run`, and `screenplay_writer` instead of switching to low-level mutation tools mid-flight.
Trust `job.progress` and `job.client_guidance` for long-running work. Beat, scene, and screenplay jobs on feature and TV templates can legitimately take several minutes (short-format templates such as advertisement and one_scene usually finish in about a minute); keep polling `job_get` rather than restarting the workflow.
Set `include_result=true` when the job is completed and you want the final generated data rather than only progress metadata.
When not to use
Do not use to start a new async workflow.
Examples
“Get the status of job_123.”
Anti-examples
- Start a new continuity audit.
Backend capabilities
Input schema
{
"$ref": "./job.get.input.json"
}Output schema
{
"$ref": "./job.get.output.json"
}