jobs

Call jobs.read

'is my clip done yet', 'did that edit finish' — read one long-running job's status by the job_id a call answered (videos.generate_clip, or an edit or draft that answered in_flight): queued, running, succeeded or failed, when it started and finished, and once it has succeeded what to read next. It changes nothing and starts nothing. Not for starting work — call the verb that makes it.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/jobs.read

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/jobs.read
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

job_idstring required

The job_id a long-running call answered (for example videos.generate_clip).

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

No recorded changes to this operation across all 6 revisions of this API.