update_ticket

Rewrites a ticket’s text. Each field you pass overwrites the stored value outright, so send the complete new text rather than a fragment or a diff — read the current ticket with get_ticket first if you are amending rather than replacing. Use it to record clarifications the person has approved, or to sharpen a vague spec before implementing it. Pass at least one of title, summary, or body; a call with none of them is an error.

Input

string

required

Id of the Montra ticket (UUID).

string

Replacement title. Trimmed; 1–300 characters.

string

Replacement one-line gist. Trimmed; up to 1000 characters.

string

Replacement markdown implementation spec.

Output

object

required

Show properties

string

required

Ticket id.

string

required

Id of the document the ticket belongs to.

string

required

Title after the update.

string

required

One-line gist after the update. Empty string when the ticket has none.

string

required

Markdown implementation spec after the update. Empty string when the ticket has none.

string

required

todo or done.

string

required

Opaque ordering key that places the ticket within its document.

number

required

Offset into the source recording, in milliseconds, that the ticket points at.

string

required

Id of the input whose generation produced this ticket. null for hand-added tickets.

string

required

ISO 8601 creation timestamp.

string

required

ISO 8601 timestamp of this update.

Notes

Fields you omit are left untouched. Fields you pass are replaced wholesale — there is no append or patch mode.
The edit is flagged as a manual edit, so a generation still running in the background will not overwrite what you wrote.
Tickets outside the workspace this connection is bound to read as not found. See workspace binding.
Related: get_ticket, set_ticket_status, and the agent workflow guide.

Get started

Guides

Tool reference

Input

Output

Notes

​Input

​Output

​Notes

Input

Output

Notes