statuscake

Update an uptime check

statuscake_update_uptime_check

Destructive

Change an uptime check's settings. Only the fields you pass are changed; list fields (tags, contact_groups, regions, dns_ips) are REPLACED, and an empty list clears them. Pass paused=true to pause a check and paused=false to resume it. StatusCake: PUT /uptime/{test_id}.

Input Schema

TableJSON Schema

Name	Required	Description
`host`	No	Name of the hosting provider (informational).
`name`	No	New name for the check.
`port`	No	Destination port (TCP, SMTP, SSH checks).
`tags`	No	Tags for the check. An empty list clears them.
`paused`	No	true to pause the check (stops running and alerting), false to resume.
`dns_ips`	No	IP addresses the DNS record must resolve to (DNS checks).
`regions`	No	Region codes to run the check from (see statuscake_list_uptime_locations).
`test_id`	Yes	The uptime check id.
`timeout`	No	Seconds to wait for the first byte, 5-75 (default 15).
`use_jar`	No	Enable cookie storage between requests.
`post_raw`	No	Raw HTTP POST body to send.
`post_body`	No	JSON object string submitted with the request; setting it makes the check use HTTP POST.
`check_rate`	No	Seconds between checks: 0, 30, 60, 300, 900, 1800, 3600 or 86400.
`dns_server`	No	Nameserver to query (DNS checks).
`user_agent`	No	Custom User-Agent sent with each check.
`do_not_find`	No	Invert find_string: the check is down if the string IS present.
`find_string`	No	String to look for in the response; the check is down if not found.
`website_url`	No	New URL, FQDN or IP address to check.
`confirmation`	No	Number of confirmation servers that must agree before alerting, 0-3 (default 2).
`trigger_rate`	No	Minutes to wait before sending an alert, 0-60 (default 0).
`custom_header`	No	JSON object string of headers to send, e.g. {"X-Env":"prod"}.
`basic_password`	No	HTTP basic-auth password for the target.
`basic_username`	No	HTTP basic-auth username for the target.
`contact_groups`	No	Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them.
`final_endpoint`	No	Where the redirect chain should end (with follow_redirects).
`include_header`	No	Include response headers in the find_string search.
`enable_ssl_alert`	No	Alert when the site's SSL certificate is about to expire.
`follow_redirects`	No	Follow redirects when testing (off by default).
`status_codes_csv`	No	Comma-separated HTTP status codes that count as down, e.g. "500,502,503".

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only flag destructiveHint=true; the description adds the critical behavioral detail an agent needs — list fields (tags, contact_groups, regions, dns_ips) are REPLACED rather than merged, and an empty list clears them, which is exactly the destructive data-loss scenario. This is meaningful context well beyond the annotation.

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?

Three compact sentences, front-loaded with the mutation contract and the destructive caveat before the pause/resume helper and endpoint reference. No filler.

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?

For a 29-parameter destructive mutation with no output schema and full schema coverage, the description supplies the missing cross-field semantics well. It omits anything about permissions/auth or error behavior, but those are not essential to calling it correctly.

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 per-parameter descriptions already carry most semantics (baseline 3). The description adds cross-cutting meaning the schema cannot express: that omitted fields are untouched and that list parameters overwrite rather than append — non-obvious behavior for 29 parameters.

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 an uptime check's settings') and even names the underlying endpoint (PUT /uptime/{test_id}). It is immediately distinguishable from the create/get/list siblings by the update semantics conveyed.

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?

Explains the partial-update contract (only passed fields change) and gives a concrete use case for paused (true=pause, false=resume), which tells the agent how to invoke it. It stops short of naming when NOT to use it or pointing to alternatives among the many sibling tools.

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

All statuscake 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.

Update an uptime check

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources