List JSM on-call schedules
jsm_list_schedulesList on-call schedules from JSM Operations to retrieve schedule IDs, owning teams, and timezones, helping you find rotation IDs for on-call queries or review existing rotations.
Instructions
List the on-call schedules configured in JSM Operations, with their ids, owning teams and timezones.
Start here when you need a schedule id for jsm_get_on_call or jsm_get_next_on_call, or when you want to know which rotations exist at all.
Args:
limit (number): 1-100, default 20
offset (number): records to skip, default 0
response_format ('markdown' | 'json'): default 'markdown'
Returns (json format): { "schedules": [ { "id": string, "name": string, "description": string, "timezone": string, "enabled": boolean, "ownerTeam": { "id": string, "name": string } } ], "pagination": { "count": number, "offset": number, "has_more": boolean, "next_offset": number } }
Examples:
"What on-call rotations do we have?" -> no args
"Find the schedule id for the platform rotation" -> then match on name
Error handling:
HTTP 401 here while alert tools work means the token is missing read:ops-config:jira-service-management — schedules and on-call sit behind a different scope from alerts, so this is a scope gap, not a bad credential.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of records to return (1-100, default 20). | |
| 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 |
|---|---|---|---|
| schedules | Yes | ||
| pagination | Yes |