SolidPing

Update status page

update_status_page

Idempotent

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

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

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.

First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses PATCH semantics, that omitted fields keep their current values, that slug collisions are rejected, that mcp:read tokens are refused, and that at least the user role is required. These are material behavioral and authorization details not captured by the structured annotations.

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

Conciseness5/5

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

The description is compact and front-loaded with the core action, then adds semantics, alternatives, and authorization constraints without repeating schema field documentation. Every sentence carries useful information.

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 with full schema coverage, annotations, and an output schema, the description covers the key prerequisites and semantics an agent needs. Return-value details are omitted appropriately because an output schema exists.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 15 fields in detail. The description adds useful global semantics about PATCH behavior and slug rejection, but it does not add field-level meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: update an existing status page by UID or slug, and return the updated page. It also distinguishes this tool from create_status_page and delete_status_page, so an agent can place it correctly among siblings.

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?

It explicitly says when to use this tool versus alternatives: use create_status_page to make a new page and delete_status_page to remove one. It also states the precondition that the page must already exist, leaving little to inference.

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

All SolidPing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.