Create status page
create_status_pageCreate a status page displaying selected monitors' current status and recent history for users without login access. Private by default; set visibility to public to share.
Instructions
Requires the write scope or higher. Creates a status page: one page showing the current status and recent history of a chosen set of monitors, for people who cannot log in to the project. Pages are private unless visibility is 'public', which publishes every monitor name on the page.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>"
},
"name": "create_status_page"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Optional URL slug, shown in the public link (/status/<slug>). Has to match ^[a-z0-9][a-z0-9-]{1,48}[a-z0-9]$ (3-50 chars, lowercase alphanumeric and hyphens). Slugs are unique across all projects, so a taken one returns 409. Omitted: a random unguessable slug, the safer default for a public page. | |
| title | Yes | Human-readable page title, e.g. 'Acme API Status'. Shown at the top of the page, and to anyone the page is shared with. | |
| check_ids | No | Comma-separated monitor UUIDs to show on the page, in no particular order, from list_monitors. Every id has to belong to this project: an unknown or cross-project id returns 400 and nothing is saved. An empty value is legal and produces a page with no monitors. | |
| visibility | No | 'private' (default) or 'public'. A public page is served at an unguessable but unauthenticated URL: anyone with the link sees the title, every monitor's name (often internal, such as 'billing-reconciler') and its up/down history. The free tier allows one public page per project; a second returns 403. |