Skip to main content
Glama

Change a status page's monitors and groups

update_status_page_components
Idempotent

Replaces the monitors a status page shows, in order, each optionally in a named group ("API", "EU region"); a group sits where its first monitor is and shows their worst state. Every plan. Free.

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": {
      "status_page_id": "<status_page_id>"
    },
    "name": "update_status_page_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupsNoGroups' settings by name: collapsed, and id (from list_status_pages) to rename a group and keep its badges working.
componentsNoThe monitors the page shows, in order, each once. Leave out to change only the groups' settings.
status_page_idYesStatus page ID from list_status_pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only but non-destructive idempotent write; the description adds real behavioral detail beyond them, namely that the monitor list is replaced wholesale and that a group is positioned by its first monitor and surfaces the worst member state. 'Every plan. Free.' conveys that no plan gating applies, which is useful context. Remaining gaps include auth/review requirements and whether changes take effect immediately.

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

Conciseness3/5

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

The core sentence is dense but earns its place, covering replacement, ordering, grouping, and group placement behavior. The trailing fragment 'Every plan. Free.' is ambiguous and reads as a truncated pricing note rather than actionable guidance, which weakens the structure. Front-loading is good, but the last sentence does not clearly justify itself.

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

Completeness3/5

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

With only three parameters, full schema coverage, and annotations covering the safety profile, most of the burden is elsewhere. However, the definition omits meaningful operational context for a whole-list replacement on a public status page: what happens to monitors left out, whether an approval step (accept_page_change) is required, and whether writes are immediately visible to visitors. These gaps matter for a replacement operation but are not fatal.

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 schema already documents all three parameters in depth, establishing a baseline of 3. The description reinforces ordering ('in order') and group semantics ('a group sits where its first monitor is and shows their worst state'), which aids interpretation of the components and groups arrays. It adds little on status_page_id or the rename-by-id mechanics beyond what the schema states.

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

Purpose4/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: it replaces the ordered set of monitors a status page shows and defines optional named groups. The scope is clear enough that an agent can distinguish it from monitor-level tools like update_monitor. It stops short of naming any sibling or stating the boundary explicitly, which keeps it at 4 rather than 5.

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?

Usage is only implied through the word 'Replaces', which signals a full overwrite rather than an incremental edit. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance (for example how this relates to accept_page_change or list_status_pages). The relevant partial-update case ('leave out components to change only groups') lives in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources