Home / Servers / PagerDuty API / list_incident_alerts
List alerts for an incident
An MCP tool from the PagerDuty API server, hosted on mcp.hjlabs.in.
List alerts for an incident List alerts for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the API Concepts Document Scoped OAuth… [GET /incidents/{id}/alerts]
Name on the gateway: pagerduty_api__list_incident_alerts · read-only.
Parameters
| Name | Type | Description |
|---|---|---|
id required | string | The ID of the resource. |
limit | integer | The number of results per page. |
offset | integer | Offset to start pagination search results. |
total | boolean | By default the total field in pagination responses is set to null to provide… |
alert_key | string | Alert de-duplication key. |
statuses[] | triggered | resolved | Return only alerts with the given statuses. (More status codes may be… |
sort_by | created_at | resolved_at | created_at:asc | created_at:desc | resolved_at:asc | resolved_at:desc | Used to specify both the field you wish to sort the results on… |
include[] | services | first_trigger_log_entries | incidents | Array of additional details to include. |
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": "pagerduty_api__list_incident_alerts",
"arguments": {
"id": "…"
}
}Or connect the PagerDuty API server directly, which lists 459 tools including this one:
claude mcp add --transport http hj-pagerduty-api https://mcp.hjlabs.in/mcp/pagerduty-api \
--header "Authorization: Bearer YOUR_API_KEY"Try asking
Use the list alerts for an incident tool with id set to ….