Call shorts.assign_filming
Pass the filming of a short to a teammate — 'have Sam film this short', 'assign this to someone on my team'. Hand the filming of a short to a teammate. They get an in-app note and an email with the beats, and the short shows on their front door as waiting on them. Calling it raises the approval card, which is the person's confirmation, so call it on the ask. Pass the teammate's NAME as the person said it; it is resolved against this workspace's members server-side. If more than one person matches, the refusal names them — ask which one rather than choosing. Not for matching footage to beats — that is shorts.find_beats. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do 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.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/shorts.assign_filming
- Auth: HTTP bearer
Headers
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
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.
Changes
No recorded changes to this operation across all 7 revisions of this API.