delete_canned_reply
Remove a saved support reply from a project's picker. Replies already sent with it are untouched.
Take a snippet out of the picker for good. Messages that were sent using it are ordinary messages on their threads and are not affected — a snippet is a template, not a link.
Confirm before calling
There is no undo and no soft delete. Confirm the target canned_reply_id with
a human — read it back with get_canned_reply
so they see the text they are losing. The tool is annotated destructive so a
client can prompt for confirmation.
Emits support.canned_reply.deleted with a snapshot of the snippet taken before it went. Idempotent in the only sense a delete can be: a second call for the same id is RESOURCE_NOT_FOUND, indistinguishable from an id that never existed.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time.
Arguments
project_id*stringUUID of the project the snippet belongs to.
canned_reply_id*stringUUID of the saved reply to remove.
What it returns
{ "data": { "canned_reply_id": "5d2f8a71-3c9e-4b06-a8f4-1e7c9d2b6a35", "deleted": true }}The id is echoed as sent. Nothing else about the snippet is returned, so read it first if the text matters.
How it fails
VALIDATION_FAILEDthe token's owner is on the project's team but their role lacks the support permission on it.
RESOURCE_NOT_FOUNDproject_id names a project the token cannot see, or canned_reply_id is unknown, already deleted, or belongs to another project.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks support-canned-reply:delete.
How is this guide?
Last updated on