Update a JSM alert's priority, message or description
jsm_update_alert_fieldOverwrite an alert's priority, message, or description to correct it when new information is known. Read the current value first to avoid destroying existing context.
Instructions
Overwrite one field on an existing JSM alert: its priority, its message, or its description.
This is how an alert gets corrected once triage knows more than the integration that raised it did — a P3 that turns out to be customer-facing, a message that says "check failed" when it should say which check, a description that should carry what has been tried.
Args:
alert_id (string): the full alert id (not the tinyId)
field ('priority' | 'message' | 'description'): which field to overwrite
value (string): the new value
There are no 'user' or 'source' arguments here, unlike the other write tools: these three endpoints take only the value.
Returns: { "requestId": string, "result": string, "alert_id": string }
IMPORTANT: this action is asynchronous. Verify with jsm_get_request_status using the returned requestId.
This overwrites, it does not append. Reading the current value first with jsm_get_alert is the difference between adding context to a description and destroying what someone else wrote in it. If you mean to add to the record without replacing anything, use jsm_add_alert_note instead — notes are additive and are what the activity timeline is for.
For field='priority', value must be exactly one of P1, P2, P3, P4, P5 — not "high", not "1", not "p1".
Examples:
"This is worse than we thought, make it a P1" -> field="priority", value="P1"
"Fix the alert title to name the failing endpoint" -> read it first, then field="message"
Constraints and errors:
Raising priority may change who is paged, since routing and escalation rules read it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| field | Yes | Which field to overwrite. Each is a separate endpoint under the hood. | |
| value | Yes | The new value. For field='priority' this must be exactly one of P1, P2, P3, P4, P5. For 'message' keep it to one line — it is the headline responders read first. For 'description' anything goes, and an empty string clears it. | |
| alert_id | Yes | Full alert id, e.g. '9b251e07-73c9-4907-9996-8cb53a6a20d0-1704440650350'. This is NOT the short tinyId shown in the JSM UI — get the full id from jsm_list_alerts first. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | No | ||
| alert_id | Yes | ||
| requestId | No |