Skip to main content
Tool Name: manage_incidentsCategory: IncidentsMode: Write (requires --enable-write-tools flag)

​
Overview

The manage_incidents tool allows you to update one or more incidents simultaneously. You can change the status (acknowledge or resolve), modify urgency, reassign to different users, or escalate to a higher level.
This tool requires write mode to be enabled. See Write Mode Configuration for details.

​
Parameters

​
incident_ids
list[string]
required
List of incident IDs to update. Can be one or more incident IDs.Example: ["Q1234567890ABCDE", "Q0987654321ZYXWV"]
​
status
string
Change the status of the incidents.Allowed values:
  • acknowledged - Mark incidents as acknowledged
  • resolved - Mark incidents as resolved
You cannot change an incident back to triggered status using this tool.
Example: "acknowledged"
​
urgency
string
Change the urgency level of the incidents.Allowed values:
  • high - High urgency
  • low - Low urgency
Example: "high"
​
assignement
UserReference
Reassign the incidents to a different user.
Note: The parameter name has a typo in the API (“assignement” instead of “assignment”). Use the exact spelling shown.
​
id
string
required
The ID of the user to assign the incidents to.Example: "PXXXXXX"
Example: {"id": "PXXXXXX"}
​
escalation_level
integer
Escalate the incidents to a specific level in the escalation policy.Example: 2 (escalate to level 2)

​
Usage Examples

​
Acknowledge multiple incidents

{
  "incident_ids": ["Q1234567890ABCDE", "Q0987654321ZYXWV"],
  "status": "acknowledged"
}

​
Resolve an incident

{
  "incident_ids": ["Q1234567890ABCDE"],
  "status": "resolved"
}

​
Reassign an incident to another user

{
  "incident_ids": ["Q1234567890ABCDE"],
  "assignement": {
    "id": "PXXXXXX"
  }
}

​
Change urgency to high

{
  "incident_ids": ["Q1234567890ABCDE"],
  "urgency": "high"
}

​
Escalate to level 2

{
  "incident_ids": ["Q1234567890ABCDE"],
  "escalation_level": 2
}

​
Combine multiple updates

{
  "incident_ids": ["Q1234567890ABCDE"],
  "status": "acknowledged",
  "urgency": "high"
}
When multiple update operations are specified, they are applied sequentially. The response only reflects the final operation. Consider this when combining multiple updates.

​
Response Format

Returns a ListResponseModel[Incident] containing the updated incidents.
​
response
list[Incident]
List of updated incident objects.
​
id
string
The incident ID.
​
incident_number
integer
The incident number.
​
status
string
Updated status of the incident.
​
title
string
The incident title.
​
updated_at
datetime
When the incident was last updated (will reflect the recent change).
​
service
ServiceReference
The associated service.
​
assignments
list[Assignment]
Current assignments (updated if reassignment was performed).

​
Common Errors

Write mode not enabled
Write operations are disabled. Enable with --enable-write-tools flag.
Solution: Restart the MCP server with the --enable-write-tools flag.
Incident not found
404 Not Found: One or more incidents were not found
Solution: Verify all incident IDs are correct and accessible.
Invalid user for assignment
400 Bad Request: User not found or not authorized
Solution: Verify the user ID is correct and the user has access to the service.
No updates specifiedIf you don’t specify any update fields (status, urgency, assignment, or escalation_level), the tool will return an empty response as no changes were made.Solution: Specify at least one field to update.

​
Best Practices

  • Acknowledge incidents when you start investigating to signal ownership
  • Update urgency if the impact is different than initially assessed
  • Reassign incidents when the appropriate subject matter expert is identified
  • Resolve incidents only when the issue is fully mitigated and verified
  • Use bulk updates to efficiently manage related incidents

list_incidents

Find incidents to manage

get_incident

Get details before updating

add_note_to_incident

Document investigation progress

add_responders

Request additional help

​
Source Reference

Function: manage_incidents in pagerduty_mcp/tools/incidents.py:141 Models: IncidentManageRequest, Incident in pagerduty_mcp/models/incidents.py

Build docs developers (and LLMs) love

Get started for freeTalk to us