Home / Servers / Linode API / put_alert_definition
Update an alert definition
An MCP tool from the Linode API server, hosted on mcp.hjlabs.in.
Update an alert definition __Beta__ Update an existing alert definition. You need read_only access to the scope for the selected serviceType. Only include the objects in the request that you want to update. Leave any object… [PUT /v4/monitor/services/{serviceType}/alert-definitions/{alertId}]
Name on the gateway: linode_api__put_alert_definition · may change things.
Parameters
| Name | Type | Description |
|---|---|---|
serviceType required | string | The Akamai Cloud Computing service being monitored. To see… |
alertId required | integer | The unique identifier assigned to the alert definition.… |
channel_ids | array | The identifiers for the alert channels to use for the alert. Run the List… |
description | string | An additional description for the alert definition. |
entity_ids | array | The id for each individual entity from a service_type. Get this value by… |
label | string | The name of the alert definition. This is used for display purposes in Akamai… |
rule_criteria | object | Details for the rules required to trigger the alert. |
severity | 0 | 1 | 2 | 3 | The severity of the alert. Supported values include 3 for info, 2 for low, 1… |
status | enabled | disabled | The current status of the alert. You can set this to enabled or disabled. |
trigger_conditions | object | The conditions that need to be met to send a notification for the alert. |
How to call it
Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:
{
"name": "linode_api__put_alert_definition",
"arguments": {
"serviceType": "…",
"alertId": 0
}
}Or connect the Linode API server directly, which lists 439 tools including this one:
claude mcp add --transport http hj-linode-api https://mcp.hjlabs.in/mcp/linode-api \
--header "Authorization: Bearer YOUR_API_KEY"Try asking
Use the update an alert definition tool with serviceType set to ….