update_ticket
Update an open support ticket. Use fetch_open_tickets first to get the case_id. Only open tickets can be updated. FORMAT: Only these HTML tags are allowed in description: , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use — it creates ugly blank blocks in the UI. Use for line breaks within text only.
update_ticket
When to use
Update an open support ticket. Use fetch_open_tickets first to get the case_id. Only open tickets can be updated. FORMAT: Only these HTML tags are allowed in description: , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use — it creates ugly blank blocks in the UI. Use for line breaks within text only.
Parameters to validate before calling
case_id (string, required) — The case number of the ticket to update
title (string, optional) — New ticket subject (max 200 characters)
description (string, optional) — New ticket description (max 20,000 characters). Allowed HTML: , , , , . No scripts, iframes, or executable code.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"case_id": "<case_id>"
},
"name": "update_ticket"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | New ticket subject (max 200 characters) | |
| case_id | Yes | The case number of the ticket to update | |
| description | No | New ticket description (max 20,000 characters). Allowed HTML: <b>, <strong>, <i>, <hr>, <br>. No scripts, iframes, or executable code. |