Skip to main content

Incidents

Incidents are the core of PagerDuty โ€” they represent service disruptions that require attention. This domain has the largest tool set with 10 tools covering listing, investigation, creation, and management.

Toolsโ€‹

list_incidentsโ€‹

List incidents with optional filtering.

ParameterTypeRequiredDescription
query_modelIncidentQueryNoOptional filtering parameters (status, urgency, service, team, date range, etc.)

Example prompts:

"List all open high-urgency incidents"

"Show me incidents from the last hour"


get_incidentโ€‹

Get a specific incident by ID or incident number.

ParameterTypeRequiredDescription
incident_idstringYesThe ID or number of the incident to retrieve
query_modelGetIncidentQueryNoOptional query parameters for additional information to include

Example prompt:

"Get details for incident P123456"


get_outlier_incidentโ€‹

Get outlier incident analysis for a given incident on its service. Returns incidents that deviate from expected patterns for the same service.

info

This feature requires the Event Intelligence package or Digital Operations plan.

ParameterTypeRequiredDescription
incident_idstringYesThe ID of the incident to get outlier information for
query_modelOutlierIncidentQueryNoQuery parameters including date range and additional details

get_past_incidentsโ€‹

Get past incidents related to a specific incident. Returns incidents within the past 6 months with similar metadata generated on the same service. Returns up to 50 past incidents by default.

info

This feature requires the Event Intelligence package or Digital Operations plan.

ParameterTypeRequiredDescription
incident_idstringYesThe ID of the incident to get past incidents for
query_modelPastIncidentsQueryNoQuery parameters including limit and total flag

Get related incidents for a specific incident. Returns the 20 most recent related incidents that are impacting other responders and services.

info

This feature requires the Event Intelligence package or Digital Operations plan.

ParameterTypeRequiredDescription
incident_idstringYesThe ID of the incident to get related incidents for
query_modelRelatedIncidentsQueryNoQuery parameters including additional details

list_incident_notesโ€‹

List all notes for a specific incident.

ParameterTypeRequiredDescription
incident_idstringYesThe ID of the incident to retrieve notes from

create_incident (write)โ€‹

Create a new incident.

ParameterTypeRequiredDescription
create_modelIncidentCreateRequestYesThe incident creation request (title, service, urgency, etc.)
note

Requires --enable-write-tools flag.

Example prompt:

"Create a high-urgency incident titled 'Payment gateway down' on the payments service"


manage_incidents (write)โ€‹

Manage one or more incidents by changing status, urgency, assignment, or escalation level. Use this tool for bulk updates.

The manage_request model accepts these flat fields:

  • incident_ids โ€” list of incident IDs to update
  • status โ€” new status (e.g., acknowledged, resolved)
  • urgency โ€” high or low
  • assignment โ€” UserReference with id field
  • escalation_level โ€” integer
ParameterTypeRequiredDescription
manage_requestIncidentManageRequestYesIncident IDs and fields to update
note

Requires --enable-write-tools flag.

Example prompt:

"Acknowledge all incidents assigned to user PXXXXXX"


add_responders (write)โ€‹

Add responders to an incident.

ParameterTypeRequiredDescription
incident_idstringYesThe ID of the incident to add responders to
requestIncidentResponderRequestYesResponder request data containing user IDs and optional message
note

Requires --enable-write-tools flag.


add_note_to_incident (write)โ€‹

Add a note to an incident.

ParameterTypeRequiredDescription
incident_idstringYesThe ID of the incident to add a note to
notestringYesThe note text to be added
note

Requires --enable-write-tools flag.

Example prompt:

"Add a note to incident P123456 saying 'Database failover initiated'"