Call shorts.plan_edit
Edit a short — move the hook up front, cut dead air, add captions — 'edit this short', 'clean up this cut'. Edit a short: move the hook to the first second, take the dead air out, lay the captions under the chin, decide the sound and the ending, lay it down, make three covers and watch it back. This is Goosy's work to do and it does NOT start on its own — it stops first on its approval card in the chat and runs only when the person approves it there. Never say the edit is done unless the result says so. ⚠️ NEVER NAME A CREDIT, A COST OR A PRICE: it is a paid step and it asks before taking it. Not for a clip the person filmed — that is shorts.edit_footage. 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.plan_edit
- 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 4 revisions of this API.