Skip to main content
Glama

Instatus MCP by usefulapi

Create incident

instatus_create_incident
Destructive

CREATES a new incident — this MODIFIES live status-page data and can notify subscribers. Provide name (required); optionally set the initial message, affected components, per-component impact via statuses, status, started, notify, and shouldPublish. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesIncident title (required).
notifyNoWhether to notify subscribers about this update.
statusNoIncident status.
messageNoIncident update message (Markdown supported).
page_idYesThe status page's id.
startedNoISO 8601 timestamp for when the incident started.
statusesNoPer-component impact — set each listed component's status for this event.
componentsNoComponent ids affected by this incident.
shouldPublishNoWhether the incident should be published to the status page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.