Update notification route
update_notification_routeUpdate one notification route in place. Only the fields you pass change; passing a field explicitly empty clears it (e.g. severity "" removes the severity filter), except a filter withheld from you (the route's scope_note), which stays as it is. Changing mode to exclude, or disabling a route, changes what gets delivered - verify with preview_notification_routing afterwards.
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": {
"route_id": "<route_id>"
},
"name": "update_notification_route"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Replace the single-kind filter; empty clears it. | |
| mode | No | include delivers matches; exclude suppresses them. | |
| kinds | No | Replace the kinds list. | |
| enabled | No | Enable or disable the route. | |
| priority | No | Evaluation order, lower first. | |
| route_id | Yes | Notification route id (UUID) from list_notification_routes. | |
| severity | No | Replace the severity filter; empty clears it. | |
| source_id | No | Replace the source filter; null or empty clears it (an empty source is never stored as a filter), except a source filter withheld from you (the route's scope_note), which stays as it is. At delivery today a notification's source is the id of the alert that fired, so filter on an alert id. At most 512 bytes and 4 uuids. A source you may not read answers Source not found, as preview_notification_routing does. | |
| cluster_id | No | Replace the cluster filter (UUID); null or empty clears it, except a cluster filter withheld from you (the route's scope_note), which stays as it is. | |
| kinds_negated | No | Invert the kinds list. | |
| stop_on_match | No | Stop evaluating lower-priority routes on match. | |
| application_id | No | Replace the application filter (UUID); null or empty clears it, except an application filter withheld from you (the route's scope_note), which stays as it is. | |
| destination_id | No | Re-point the route at another alert destination (UUID). | |
| reference_pattern | No | Replace the branch/tag/pull request glob filter (e.g. main, release/*, pull/*); empty clears it. |