Skip to main content
Tool Name: get_incidentCategory: IncidentsMode: Read-only

​
Overview

The get_incident tool retrieves detailed information about a specific incident by its ID or incident number. You can optionally include additional related information such as users, services, notes, and more.

​
Parameters

​
incident_id
string
required
The ID or incident number of the incident to retrieve.Example: "Q1234567890ABCDE" or "12345"
​
include
list[string]
List of additional information to include in the response.Available options:
  • users - Include user details
  • services - Include service details
  • assignments - Include assignment information
  • acknowledgers - Include who acknowledged the incident
  • custom_fields - Include custom field values
  • teams - Include team information
  • escalation_policies - Include escalation policy details
  • notes - Include incident notes
  • urgencies - Include urgency information
  • priorities - Include priority information
Example: ["users", "services", "notes"]

​
Usage Examples

​
Get basic incident information

{
  "incident_id": "Q1234567890ABCDE"
}

​
Get incident with notes and assignments

{
  "incident_id": "Q1234567890ABCDE",
  "include": ["notes", "assignments", "users"]
}

​
Get incident by incident number

{
  "incident_id": "12345",
  "include": ["services", "teams", "escalation_policies"]
}

​
Response Format

Returns an Incident object with detailed information.
​
id
string
The unique ID of the incident.
​
incident_number
integer
The incident number (unique across your account).
​
status
string
Current status of the incident.Values: triggered, acknowledged, or resolved
​
title
string
A succinct description of the nature, symptoms, cause, or effect of the incident.
​
summary
string
A short summary of the incident.
​
created_at
datetime
The time the incident was first triggered.
​
updated_at
datetime
The time the incident was last modified.
​
resolved_at
datetime
The time the incident was resolved (null if not resolved).
​
service
ServiceReference
The service the incident is associated with.
​
id
string
Service ID
​
type
string
Always “service_reference”
​
assignments
list[Assignment]
List of users assigned to the incident (included if specified in include parameter).
​
at
datetime
When the assignment was created
​
assignee
UserReference
The assigned user
​
type
string
Always returns “incident”

​
Common Errors

Incident not foundIf the incident ID doesn’t exist or you don’t have access:
404 Not Found: The incident was not found or you do not have permission to access it.
Solution: Verify the incident ID is correct and you have proper permissions.

list_incidents

List all incidents with filters

manage_incidents

Update incident status or assignment

add_note_to_incident

Add a note to the incident

list_incident_notes

View all incident notes

​
Source Reference

Function: get_incident in pagerduty_mcp/tools/incidents.py:57 Models: GetIncidentQuery, Incident in pagerduty_mcp/models/incidents.py

Build docs developers (and LLMs) love

Get started for freeTalk to us