video_unit

Call video_unit.ship_status

Check one video unit's Ship step — 'what's left before this video can go out', 'is this video ready to ship'. Read one video unit's Ship step — which destinations it is going to, and which destination-metadata fields are still unanswered, with the field ids. Use it to tell someone what is left before this video can go out. You cannot ship it: handing off, starting a new version, marking it final and publishing are theirs to do on the Ship screen. Not for choosing the destinations — that is video_unit.set_destinations. If they mean the video they are looking at and name no id, CALL IT WITH NO video_unit_id: it resolves the video whose page the question was asked on, and refuses plainly when there is none. Never ask which video, and never say a video is out of reach, before trying that.

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/video_unit.ship_status

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/video_unit.ship_status
  • 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

video_unit_idstring uuid

The video unit, as a UUID. Take it from the conversation's context — never invent one. OMIT it when the person is looking at the video and means that one: the tool resolves the unit whose page the question was asked on, and refuses plainly when there is none. Never ask which video before trying that.

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.