PagerDuty MCP Server

get_incidents

Retrieve PagerDuty incidents filtered by service, team, status, urgency, or date range, or get details for a specific incident ID. Includes options for related incidents and notes.

Instructions

Get PagerDuty incidents by filters or get details for a specific incident ID or number.

Input Schema

TableJSON Schema

Name	Required	Description
`incident_id`	No	The incident ID or number to retrieve (optional, cannot be used with any other filters).
`current_user_context`	No	Filter by current user's context (default: True). Not used if `incident_id` is provided.
`service_ids`	No	Filter by services (optional, excludes current_user_context). Not used if `incident_id` is provided.
`team_ids`	No	Filter by teams (optional, excludes current_user_context). Not used if `incident_id` is provided.
`statuses`	No	Filter by status (optional). Not used if `incident_id` is provided. Must be input as a list of strings, valid values are `["triggered", "acknowledged", "resolved"]`. Defaults to all statuses.
`urgencies`	No	Filter by urgency (optional). Not used if `incident_id` is provided. Must be input as a list of strings, valid values are `["high", "low"]`. Defaults to all urgencies. Account must have the urgencies ability to do this.
`since`	No	Start of query range in ISO8601 format (default range: 1 month, max range: 6 months). Not used if `incident_id` is provided.
`until`	No	End of query range in ISO8601 format (default range: 1 month, max range: 6 months). Not used if `incident_id` is provided.
`limit`	No	Max results (optional). Not used if `incident_id` is provided.
`include_past_incidents`	No	If True and `incident_id` is provided, includes similar past incidents in the response. Defaults to False. Cannot be used without `incident_id`.
`include_related_incidents`	No	If True and `incident_id` is provided, includes related incidents impacting other services/responders in the response. Defaults to False. Cannot be used without `incident_id`.
`include_notes`	No	If True, includes notes for each incident in the response. Defaults to False.
`include`	No	List of fields to include in the response. If specified, only these fields will be returned for each incident

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Tool Definition Quality

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility. It only states 'Get', implying a read operation, but fails to mention any behavioral traits such as authentication requirements, rate limits, or that it performs no side effects. The description adds minimal value beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single 13-word sentence that front-loads the core purpose. Every word is meaningful, with zero redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (13 parameters, dual mode) and the presence of an output schema, the high-level description is adequate but leaves the agent to rely heavily on the schema. More context about when to use filters vs. ID or typical use cases would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3. The tool description adds no additional meaning to the parameters beyond what the schema already provides, so no extra credit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it retrieves incidents either by filters or by a specific incident ID/number, clearly distinguishing the two modes. The verb 'Get' and resource 'incidents' are specific, and it differentiates from sibling write tools like acknowledge_incident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description outlines two usage modes (filter vs. specific ID) but does not provide guidance on when to use this tool over siblings like get_services or get_teams. There is no explicit 'when to use' or 'when not to use' context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wpfleger96/pagerduty-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server