list_incidents
Retrieve and filter PagerDuty incidents by service IDs, team IDs, statuses, and date ranges. Streamline incident management using structured criteria for efficient workflow optimization.
Instructions
List PagerDuty incidents based on specified filters.
Args: current_user_context (bool): Boolean, use the current user's team_ids and service_ids to filter (default: True, cannot be used with service_ids or team_ids) service_ids (List[str]): list of PagerDuty service IDs to filter by (optional, cannot be used with current_user_context) team_ids (List[str]): list of PagerDuty team IDs to filter by (optional, cannot be used with current_user_context) statuses (List[str]): list of status values to filter by (optional). Valid values are: - 'triggered' - The incident is currently active (included by default) - 'acknowledged' - The incident has been acknowledged by a user (included by default) - 'resolved' - The incident has been resolved (excluded by default) since (str): Start of date range in ISO8601 format (optional). Default is 1 month ago until (str): End of date range in ISO8601 format (optional). Default is now
Returns: Dict[str, Any]: Dictionary containing metadata (count, description) and a list of incidents matching the specified criteria
Input Schema
Name | Required | Description | Default |
---|---|---|---|
current_user_context | No | ||
service_ids | No | ||
since | No | ||
statuses | No | ||
team_ids | No | ||
until | No |
Input Schema (JSON Schema)
You must be authenticated.
Other Tools from PagerDuty MCP Server
Related Tools
- @osomai/servicenow-mcp
- @DynamicEndpoints/huntress-mcp-server
- @wpfleger96/pagerduty-mcp-server
- @GeLi2001/datadog-mcp-server
- @wpfleger96/pagerduty-mcp-server