BeatBandit MCP

Tools

/

Jobs

/

job_get

job_get

read
beta
auth: project:read
approval: never
status: v1

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`, MCP-owned `screenplay_writer`, and Novel parent jobs.

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.

Completed Novel parents with canonical results set `finalize_required=false` and `job.result.finalized=true`, then return the saved-artifact or author-review action. Voice jobs expose the complete proposal resource and apply actions only while their source Voice revisions remain current.

Running Novel Blueprint, Chapter Outline, Voice, Writer, and Audit parents are long-running backend-owned jobs with a minimum 20-second poll cadence. Poll at the cadence in `job.progress`; the parent persists its result at completion and no client finalize call is required.

Terminal progress uses a terminal label and caps `elapsed_seconds` at `completed_at`; repeated reads do not make a completed job appear to keep running.

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

job.get

Linked resources

Tool calls may return resource_links pointing at these resource families.

novel_manuscriptnovel_voice_proposal

Input schema

job_get input
{
  "$ref": "./job.get.input.json"
}

Output schema

job_get output
{
  "$ref": "./job.get.output.json"
}

← All toolsv1 · query_tool