Visual Sentinel

Change a status page

vs_status_pages_update

DestructiveIdempotent

Change a status page: title, address, visibility, uptime and history shown, subscriptions, order, colors and search text (Business and Agency), custom CSS and logos (Agency), and IP allowlist. Send only the fields to change. A visitor password is set in the dashboard.

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": {
      "id": "<id>"
    },
    "name": "vs_status_pages_update"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Status page id.
`logo`	No	Logo address: an https image address, or empty to remove (Agency).
`name`	No	Page title.
`slug`	No	Address part of the page, for example acme for /status/acme.
`theme`	No	Colors and font (Business and Agency): { primaryColor, bgColor, textColor, accentColor } as #RGB or #RRGGBB, and fontFamily, one of Inter, System, Roboto, Open Sans, Lato, Poppins, Montserrat, Source Sans Pro, Nunito, Raleway. null clears it.
`public`	No	true publishes the page, false hides it.
`favicon`	No	Browser tab icon (Agency).
`ogImage`	No	Share image address (Business and Agency).
`darkLogo`	No	Logo for dark mode (Agency).
`sortMode`	No	Order of monitors: MANUAL, NAME or STATUS.
`customCss`	No	Custom CSS (Agency, up to 10,000 characters). Unsafe rules are removed.
`metaTitle`	No	Search title (Business and Agency, up to 60 characters).
`allowedIps`	No	IP addresses or ranges allowed when ipAllowlistEnabled is on.
`showUptime`	No	Show uptime bars.
`uptimeDays`	No	Days of uptime shown: 30, 60, 90, 180 or 365.
`description`	No	Short text under the title (up to 500 characters).
`historyDays`	No	Days of history shown (1 to 365).
`showHistory`	No	Show past incidents.
`metaKeywords`	No	Up to 10 keywords (Business and Agency).
`metaDescription`	No	Search description (Business and Agency, up to 160 characters).
`allowSubscribers`	No	Let visitors subscribe to updates.
`ipAllowlistEnabled`	No	Only let listed addresses see the page. Needs a verified custom domain.
`incidentHistoryDays`	No	Days of incident history: 0, 30, 90, 180 or 365.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The description adds behavior the annotations don't carry: partial-update semantics (omitted fields stay as-is), plan-tier gating for many fields (Business/Agency), and the fact that the visitor password cannot be set here but only in the dashboard. It does not explain the destructiveHint=true consequence (e.g. overwriting customCss or clearing theme with null), which is the one meaningful gap.

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 the action, and the two trailing sentences carry distinct, useful information. The long field enumeration overlaps heavily with the schema and is the weakest part, but overall it stays compact for a 23-parameter tool.

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

Completeness4/5

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

With a rich 23-param schema at full coverage and annotations present, the description covers action, partial-update rule, and tier gating. It would be stronger if it flagged that null clears a theme or that CSS is sanitized, but nothing essential for a correct call is missing.

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 coverage is 100%, so the baseline is 3; the description's field list is essentially a restatement of the schema properties. The only added semantic is the note that the visitor password lives in the dashboard, which is marginal.

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 and resource ('Change a status page') and enumerates the editable surface (title, address, visibility, uptime/history, subscriptions, order, colors, CSS, allowlist). That distinguishes it from vs_status_pages_create and vs_status_pages_get without either schema being opened.

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

Usage Guidelines3/5

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

'Send only the fields to change' is real invocation guidance for a partial update. However, no alternatives are named (vs_status_pages_create for new pages, vs_status_page_monitors_* for monitor assignment), and no prerequisites or when-not conditions are given.

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

All Visual Sentinel 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.