Skip to main content
Glama

instatus

by io.usefulapi

Update component

instatus_update_component
Destructive

UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoComponent name.
orderNoDisplay order of the component on the page.
statusNoOperational status of the component.
groupedNoWhether the component is displayed within a group.
page_idYesThe status page's id.
archivedNoWhether the component is archived (hidden).
showUptimeNoWhether to show the uptime graph for this component.
descriptionNoFree-form component description.
component_idYesThe component's id to update.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Description confirms destructive nature (modifies live data) and mentions return value, aligning with annotations (destructiveHint=true). Does not disclose additional behaviors like required permissions or side effects beyond what annotations provide.

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?

Description is three sentences covering purpose, key usage, and endpoint reference. Efficient but includes redundant status enum list and endpoint URL that may not be necessary.

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?

Given 9 parameters and no output schema, description explains primary operation and return value. Lacks details on behavior for other parameters like grouped or archived, but sufficient for basic usage.

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 parameters are well documented. Description adds general usage tip ('send only fields to change') but no new semantic detail beyond schema.

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?

Clearly states it updates a component by ID and modifies live status-page data. Differentiates from sibling tools like instatus_get_component or instatus_update_incident by specifying the resource type and the primary use of setting operational status.

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

Usage Guidelines4/5

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

Describes the primary use case (setting operational status) and advises to send only changed fields. However, it does not explicitly state when not to use or mention alternatives, though sibling tool context clarifies different resources.

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

All instatus toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct resource (component, incident, maintenance, page) and action (create, get, list, update, delete). There is no overlap or ambiguity between tool purposes.

Naming Consistency5/5

All tools follow the pattern 'instatus_<action>_<resource>' in snake_case. Names are predictable and consistent across all 14 tools.

Tool Count5/5

14 tools cover the core operations for status page management (components, incidents, maintenances, pages) without being excessive. The number feels appropriate for the domain.

Completeness4/5

Incidents and maintenances have full CRUD coverage. Components lack create and delete tools, and pages have only list. These are minor gaps that may require out-of-band management.

Resources