get_ticket first if you are amending rather than replacing.
Call it only when the person explicitly asks you to change the ticket’s text — for example to record a clarification they want captured on the ticket. Never call it on your own initiative, and never to record progress: adding “implemented”, “done”, or ”✅” to a title or body overwrites the person’s spec, and there is no ticket status to set. Report progress in conversation instead. 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
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,link_ticket_issue, and the agent workflow guide.