Search JSM alerts
jsm_list_alertsSearch and list Jira Service Management Operations alerts to find open or unacknowledged issues, filter by priority, team, or tag, and convert a short tinyId into the full alert id.
Instructions
Search and list alerts in Jira Service Management Operations.
This is the entry point for almost every alert workflow: use it to find open or unacknowledged alerts, filter by priority/team/tag, and to resolve a short tinyId (as shown in the JSM UI) into the full alert id that every other alert tool requires. It reads only — it never creates or modifies alerts.
Args:
query (string, optional): field:value search, e.g. "status:open AND priority:P1"
limit (number): 1-100, default 20
offset (number): records to skip, default 0
sort (string): field to sort by, default "createdAt"
order ('asc' | 'desc'): default "desc"
response_format ('markdown' | 'json'): default "markdown"
Returns (json format): { "alerts": [ { "id": string, // full alert id — pass this to other tools "tinyId": string, // short id shown in the JSM UI "message": string, "status": "open" | "closed", "acknowledged": boolean, "priority": "P1".."P5", "count": number, // dedupe count "tags": string[], "owner": string, "createdAt": string, // ISO 8601 "lastOccurredAt": string } ], "pagination": { "count": number, "offset": number, "has_more": boolean, "next_offset": number } }
Examples:
"What's on fire right now?" -> query="status:open AND acknowledged:false", sort="createdAt"
"Show P1s from the Payments team" -> query="priority:P1 AND teams:Payments"
"Find the alert about Redis latency" -> query="message:Redis"
Constraints and errors:
offset + limit must stay below 20000; the API refuses to page deeper.
A malformed query returns HTTP 400 — field names are case-sensitive.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Field to sort by (default 'createdAt'). These four are the only values the API accepts. | createdAt |
| limit | No | Maximum number of records to return (1-100, default 20). | |
| order | No | Sort direction (default 'desc', i.e. newest first). | desc |
| query | No | JSM alert search query. Field:value syntax, combinable with AND/OR/NOT. Examples: "status:open", "status:open AND priority:P1", "acknowledged:false AND createdAt > 1704067200000", "tag:database AND status:open", "teams:Payments". Omit to return the most recent alerts unfiltered. | |
| offset | No | Number of records to skip, for paging. Use the 'next_offset' from a previous response. | |
| response_format | No | Output format. 'markdown' is compact and human-readable (default); 'json' returns every field for programmatic use. | markdown |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| alerts | Yes | ||
| pagination | Yes |