shorts

Call shorts.undo_edit

Undo one line of Goosy's edit — 'undo that last change', 'put that part back the way it was'. Take ONE line of Goosy's edit back and lay that part of the short down again. Read the log with shorts.read_edit first and use the id it gives — never a line number and never the sentence. The line stays in the log, struck through, so the person can see what they changed their mind about. Not for editing the whole short again — that is shorts.plan_edit. 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.

post/api/v1/tools/shorts.undo_edit

Request

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

short_idstring required

The short's id, as the board or a read projection gave it.

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 5 revisions of this API.