videos

Call videos.undo_edit

'undo that last change', 'put the pause back' — take back ONE thing the edit did to a video, by the log line's id videos.read_edit gives it. The line stays in the log, struck, and the video's length is worked out again; nothing is laid down again, so a master already made keeps the change until the video is edited again. It answers in two calls: without confirmation_id it names the line it would take back and changes nothing; the same call again with that confirmation_id, on a member's own API key, takes back exactly that line. Not for editing the video again — that is videos.plan_edit.

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/videos.undo_edit

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/videos.undo_edit
  • 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_idstring uuid required

The video's id, as given in this conversation.

log_entry_idstring required

The log line to undo, by the id the edit log gave it.

confirmation_idstring uuid

Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.

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.