SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

Update status page

update_status_page

Idempotent

Modify an existing status page by UID or slug, changing only provided fields and returning the updated page. Use create or delete tools to add or remove pages.

Instructions

Update an existing status page by UID or slug and return the updated page. PATCH semantics — only fields you pass change, omitted fields keep their current values; the page must already exist and a slug that collides with another page is rejected. Use create_status_page to make a new page and delete_status_page to remove one instead. Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New display name, e.g. "Public status page".
`slug`	No	New URL-friendly slug, e.g. "public".
`enabled`	No	Enable or disable the public-facing page.
`language`	No	Language code, e.g. "en" or "fr".
`customCss`	No	Custom CSS injected into the public page as a <style> element (see create_status_page). Max 64 KB; @import is rejected. Pass an empty string to clear it.
`isDefault`	No	Mark as the org's default page (only one allowed).
`identifier`	Yes	Status page UID or URL-friendly slug, e.g. "public".
`visibility`	No	Visibility setting. Allowed: "public", "private".
`autoPublish`	No	Automatically publish incidents affecting this page's resources as public incidents. New pages default to true; pages that existed before this feature shipped default to false.
`autoResolve`	No	What an auto-created publication does when its incident resolves. Allowed: "always", "if_untouched" (default — a publication a human has edited is left for them to close), "never".
`description`	No	New free-text description shown in the UI.
`historyDays`	No	Days of history to show on the page (default 90).
`showAvailability`	No	Toggle availability percentage on the public page.
`showResponseTime`	No	Toggle response-time charts on the public page.
`autoPublishDelaySeconds`	No	Debounce in seconds before an incident becomes public (default 60). 0 publishes immediately. An incident that resolves inside the delay is never published at all.

Output Schema

TableJSON Schema

Name	Required	Description
`uid`	Yes	Status page UID.
`name`	No	Display name.
`slug`	No	URL-friendly slug.
`enabled`	No	Whether the public page is served.
`createdAt`	No	RFC3339 creation timestamp.
`isDefault`	No	Whether this is the organization's default page.
`visibility`	No	"public", "private" or "password".
`historyPeriod`	No	History window: "24h", "7d", "30d" or "90d".

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.38.5Oct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "createdAt": {
+      "description": "RFC3339 creation timestamp.",
+      "type": "string"
+    },
+    "enabled": {
+      "description": "Whether the public page is served.",
+      "type": "boolean"
+    },
+    "historyPeriod": {
+      "description": "History window: \"24h\", \"7d\", \"30d\" or \"90d\".",
+      "type": "string"
+    },
+    "isDefault": {
+      "description": "Whether this is the organization's default page.",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "Display name.",
+      "type": "string"
+    },
+    "slug": {
+      "description": "URL-friendly slug.",
+      "type": "string"
+    },
+    "uid": {
+      "description": "Status page UID.",
+      "type": "string"
+    },
+    "visibility": {
+      "description": "\"public\", \"private\" or \"password\".",
+      "type": "string"
+    }
+  },
+  "required": [
+    "uid"
+  ],
+  "type": "object"
+}

First observedv0.32.1Sep 26, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: it discloses PATCH semantics (omitted fields retain values), the slug-collision rejection behavior, and required auth ('mcp scope', 'mcp:read tokens are refused', 'at least the user role'). The annotations only assert idempotent/non-destructive/closed-world; the description supplies the operational constraints an agent must satisfy before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and update semantics before alternatives and auth, so the highest-value information comes first. Dense but no sentence is filler; the auth/precondition clause is compressed into the final sentence rather than padded out.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter mutation tool, the description covers purpose, patch semantics, preconditions, failure modes (slug collision), alternatives, and authorization, while the output schema and per-parameter schema descriptions handle the rest. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description meaningfully adds the update semantics for all 15 fields ('only fields you pass change, omitted fields keep their current values'), which is the single most important fact about how these parameters behave. It also clarifies that identifier accepts either a UID or a slug.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource combination ('Update an existing status page') and immediately scopes the target as 'by UID or slug'. It also names the sibling tools for the adjacent operations (create_status_page, delete_status_page), so the agent can distinguish it from them without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'Use create_status_page to make a new page and delete_status_page to remove one instead.' It also states the precondition that the page must already exist and that a slug collision is rejected, which is exactly the when-not-to-use guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.