update-monitor

Update an existing monitor

Preflight — read first. If you cannot see any uptimerobot:* MCP tools in your tool list, invoke the uptimerobot:setup skill before doing anything else. Do not tell the user the MCP is misconfigured — setup's Step 0 detects the common case (server connected, tools loaded after session start) and resolves it without re-keying.

Uses the update-monitor tool. All updates are partial — only send the fields you want to change. Monitor type is immutable; delete and recreate if you need a different type.

Before you call

1. Resolve the monitorId with list-monitors (search by name) — never guess an ID.
2. get-monitor-details to read the current config. You'll need it for the array fields below.
3. Call update-monitor with just the changed fields.
4. get-monitor-details again to verify. Replication lag can make a follow-up list-monitors look stale.

Array fields overwrite (not merge)

assignedAlertContacts and tagNames are full replacements. To add or remove a single item, read-modify-write using the list from get-monitor-details.

Use cases

1. Rename a monitor

{ "monitorId": 800123456, "friendlyName": "Production API (us-east-1)" }

2. Change the target URL

{ "monitorId": 800123456, "url": "https://api.example.com/v2/health" }

Only valid for URL-based types (HTTP, KEYWORD, PING, PORT, DNS, API, UDP). HEARTBEAT monitors have no url — the push URL is fixed at creation.

3. Adjust the check interval

{ "monitorId": 800123456, "interval": 60 }

Range: 30–86400 seconds. 30 s is paid plans only — Free returns -28002 subscription_limit_exceeded.

4. Tune request timeout and slow-response threshold

{
  "monitorId": 800123456,
  "timeout": 15,
  "responseTimeThreshold": 2000
}

• timeout — 1–60 s. Not valid on HEARTBEAT.
• responseTimeThreshold — ms, 0 disables. Applies to every active region.

5. Heartbeat grace period