acknowledge_incident
ChatGPTAcknowledge an incident: tell the team you are looking at it, which stops it from escalating further. Optional note is recorded on the timeline.
create_status_incident
ChatGPTCreate a status-page incident, including a historical outage. Publishes immediately subject to independent outage-status and incident-detail visibility switches. A resolved historical outage accepts actual started_at and resolved_at timestamps. Subscriber notifications default to off. This creates a new statement and does not deduplicate existing incidents.
edit_status_incident
ChatGPTCorrect an existing status-page incident: title, impact, actual outage times, visibility, affected components or wording of existing updates. Requires the current title and impact. Does not send notifications, add messages or change incident state.
get_incident
ChatGPTFull detail of one incident: status, who acknowledged/resolved it, the timeline (alerts, pages sent, comments, escalations), the raw alert payload, the AI analysis (summary, probable cause, suggested action) and related incidents.
get_on_call_calendar
ChatGPTOn-call shifts overlapping a date range of up to 92 days, split around overrides. Defaults to today.
get_post_mortem
ChatGPTThe post-mortem written for an incident: impact, timeline, root cause, resolution, publication state and action items. Returns not found when no post-mortem exists.
get_post_mortem_form
ChatGPTEditable post-mortem form data: existing document, generated draft, incident facts, allowed assignees, impact types and severities. Prefill only fills blank fields in an existing draft.
get_status
ChatGPTInternal operational health: ok, attention or critical, open incidents by severity and status, newest open incidents, current on-call coverage and active maintenance for administrators.
get_status_page
ChatGPTThe signed-in status-page console: overall status, component IDs and statuses, 90-day uptime, open statements including internal details, recent history and drafts awaiting review for authorized publishers.
get_status_statement
ChatGPTOne status-page incident in the signed-in console, with its update history, visibility switches, update UUIDs and any published incident report.
list_incidents
ChatGPTList incident summaries, newest first, 20 per page, with filters for status, team and ownership.
list_my_action_items
ChatGPTPost-mortem action items assigned to you that are not done yet, soonest due first, with the incident each came from.
list_owed_post_mortems
ChatGPTIncidents still owing an unpublished post-mortem, overdue first, across your teams. Includes owner, due date and draft status. Returns up to 25 incidents.
list_post_mortem_follow_ups
ChatGPTPost-incident work still owed across your teams: resolved incidents whose post-mortem was never published, and published ones with unfinished action items. The "what are we forgetting?" list.
list_post_mortems
ChatGPTBrowse the post-mortem archive visible to the connected account, newest outage first, 25 per page. Filters include draft/published state, public/internal visibility, outstanding action items and title.
list_teams
ChatGPTThe teams visible to the connected account, including their IDs. Administrators can see all teams in their workspace.
post_status_update
ChatGPTPost a new message to a status-page incident and change its state, including resolving or reopening it. The resolved_at timestamp sets the actual outage end; the message is posted at the current time. Subscriber notifications default to off.
publish_post_mortem
ChatGPTPublish the internal post-mortem to its team. Idempotent. This does not publish the customer-facing summary.
publish_post_mortem_publicly
ChatGPTPublish the customer-facing post-mortem summary at a public URL. Requires a nonempty public_summary.
reopen_incident
ChatGPTReopen a resolved incident. Does nothing if it is not resolved. Optional note is recorded on the timeline.
resolve_incident
ChatGPTResolve an incident: the problem is over. Optional note is recorded on the timeline.
save_post_mortem
ChatGPTCreate or edit an incident post-mortem, including timeline, impact, root cause, resolution, customer-facing summary and action items. Title and impact_type are required. Omitted fields and row lists are preserved. Existing row IDs update rows; new rows omit IDs. A supplied row ID with an empty title or description deletes that row. Saving does not publish a draft; editing an already public summary changes its public page.
toggle_action_item
ChatGPTTick a post-mortem action item off, or back on if it was already done. Allowed for its assignee and the incident's team leads.
unpublish_post_mortem_publicly
ChatGPTRemove the public customer-facing report while preserving the internal post-mortem and action items.
whoami
ChatGPTThe signed-in user: name, role, timezone, language and permitted management capabilities.
whos_on_call
ChatGPTWho is on call right now, one entry per active schedule, with the schedule, team and the person (overrides applied).
acknowledge_incident
Claudecreate_status_incident
Claudeedit_status_incident
Claudeget_incident
Claudeget_on_call_calendar
Claudeget_post_mortem
Claudeget_post_mortem_form
Claudeget_status
Claudeget_status_page
Claudeget_status_statement
Claudelist_incidents
Claudelist_my_action_items
Claudelist_owed_post_mortems
Claudelist_post_mortem_follow_ups
Claudelist_post_mortems
Claudelist_teams
Claudepost_status_update
Claudepublish_post_mortem
Claudepublish_post_mortem_publicly
Claudereopen_incident
Clauderesolve_incident
Claudesave_post_mortem
Claudetoggle_action_item
Claudeunpublish_post_mortem_publicly
Claudewhoami
Claudewhos_on_call
Claude