Skip to main content
Glama

update_monitor

Modify an existing uptime monitor by ID: change its name, target, schedule, alerts, or other settings while omitted fields stay unchanged; returns the updated monitor record.

Instructions

Patch an existing monitor and return its updated record. Read get_monitor first, then send id and at least one changed field; omitted fields stay unchanged and type cannot change. Lists and headers replace their previous values, while documented nulls clear optional settings. Prefer pause_monitor/resume_monitor for a pause-only change; use this for configuration changes or a combined edit. Resuming sets status to pending; heartbeat interval/grace changes recalculate its deadline. New settings affect later checks and alerts; hosted plan limits and target restrictions still apply.

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": "update_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesResource UUID returned by the matching list tool; not its name, incident number or status-page slug.
nameNoDisplay name shown in the dashboard, alerts and status-page components.
tagsNoDashboard filter labels; a supplied list replaces the existing tags, and an empty list clears them.
methodNoHTTP request method; ignored for other monitor types.
pausedNoTrue pauses checks and alerts; false resumes checking with pending status. Prefer pause_monitor or resume_monitor for this change alone.
targetNoHTTP: absolute http(s) URL. TCP: host:port. DNS: hostname. Database/Redis: connection URL for that protocol. Heartbeat: leave empty. Public targets only by default.
headersNoHTTP request headers; replaces the header map. An empty object removes all custom headers. Existing masked values preserve stored secrets.
keywordNoHTTP response-body text to test; null disables keyword matching.
projectNoProject id (from list_workspaces). Omit to use the default project of the workspace.
regionsNoRegion ids from list_regions. auto uses this deployment; explicit regions work for HTTP/TCP only. A supplied list replaces the existing one.
graceSecNoExtra seconds allowed after a heartbeat deadline before it counts as missed; used only for heartbeat monitors.
timeoutMsNoMaximum duration of a check in milliseconds.
workspaceNoWorkspace id (from list_workspaces). Omit to use the default one.
channelIdsNoAlert-channel UUIDs from list_channels. Replaces the selected channels; an empty list clears them. Newly created monitors also inherit auto-enabled channels.
intervalSecNoSeconds between checks, or the expected heartbeat period. Hosted plans may require a longer interval.
keywordModeNoWhether the HTTP response body must contain keyword or must not contain it.
expectedStatusNoHTTP response status that counts as healthy; an expected 3xx is checked without following the redirect.
slowAlertAfterNoConsecutive slow checks required for a slow-response alert; zero disables these alerts.
slowThresholdMsNoLatency in milliseconds above which a successful check counts as slow.
expectedLocationNoFor an expected HTTP redirect (3xx), require this Location URL or path; null or empty string accepts any destination.
failureThresholdNoConsecutive failed checks required before opening an incident.
minRegionsFailingNoFailed regions needed to mark a multi-region monitor down; zero uses a majority of regions that answered.
dependsOnMonitorIdNoParent monitor UUID in the same project; suppresses new incidents and alerts while the parent is down. Null removes the dependency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changedv0.1.1
    • addedInput schema / properties / channelIds / description
      Added value: +"Alert-channel UUIDs from list_channels. Replaces the selected channels; an empty list clears them. Newly created monitors also inherit auto-enabled channels."
    • addedInput schema / properties / dependsOnMonitorId / description
      Added value: +"Parent monitor UUID in the same project; suppresses new incidents and alerts while the parent is down. Null removes the dependency."
    • addedInput schema / properties / expectedLocation
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 2048,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "For an expected HTTP redirect (3xx), require this Location URL or path; null or empty string accepts any destination."
      +}
    • addedInput schema / properties / expectedStatus / description
      Added value: +"HTTP response status that counts as healthy; an expected 3xx is checked without following the redirect."
    • addedInput schema / properties / failureThreshold / description
      Added value: +"Consecutive failed checks required before opening an incident."
    • addedInput schema / properties / graceSec / description
      Added value: +"Extra seconds allowed after a heartbeat deadline before it counts as missed; used only for heartbeat monitors."
    • addedInput schema / properties / headers / description
      Added value: +"HTTP request headers; replaces the header map. An empty object removes all custom headers. Existing masked values preserve stored secrets."
    • changedInput schema / properties / id / description
      Previous value: -"Resource id (uuid)"New value: +"Resource UUID returned by the matching list tool; not its name, incident number or status-page slug."
    • addedInput schema / properties / intervalSec / description
      Added value: +"Seconds between checks, or the expected heartbeat period. Hosted plans may require a longer interval."
    • addedInput schema / properties / keyword / description
      Added value: +"HTTP response-body text to test; null disables keyword matching."
    • addedInput schema / properties / keywordMode / description
      Added value: +"Whether the HTTP response body must contain keyword or must not contain it."
    • addedInput schema / properties / method / description
      Added value: +"HTTP request method; ignored for other monitor types."
    • addedInput schema / properties / minRegionsFailing / description
      Added value: +"Failed regions needed to mark a multi-region monitor down; zero uses a majority of regions that answered."
    • addedInput schema / properties / name / description
      Added value: +"Display name shown in the dashboard, alerts and status-page components."
    • addedInput schema / properties / paused / description
      Added value: +"True pauses checks and alerts; false resumes checking with pending status. Prefer pause_monitor or resume_monitor for this change alone."
    • addedInput schema / properties / regions / description
      Added value: +"Region ids from list_regions. auto uses this deployment; explicit regions work for HTTP/TCP only. A supplied list replaces the existing one."
    • addedInput schema / properties / slowAlertAfter / description
      Added value: +"Consecutive slow checks required for a slow-response alert; zero disables these alerts."
    • addedInput schema / properties / slowThresholdMs / description
      Added value: +"Latency in milliseconds above which a successful check counts as slow."
    • addedInput schema / properties / tags / description
      Added value: +"Dashboard filter labels; a supplied list replaces the existing tags, and an empty list clears them."
    • addedInput schema / properties / target / description
      Added value: +"HTTP: absolute http(s) URL. TCP: host:port. DNS: hostname. Database/Redis: connection URL for that protocol. Heartbeat: leave empty. Public targets only by default."
    • addedInput schema / properties / timeoutMs / description
      Added value: +"Maximum duration of a check in milliseconds."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations establish mutation, non-idempotency, and non-destructiveness. The description adds substantial behavioral detail beyond those annotations: omitted fields stay unchanged, type cannot change, lists/headers replace prior values, documented nulls clear optional settings, resuming sets status to pending, heartbeat changes recalculate deadlines, and new settings affect later checks.

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?

The description is dense but well structured and front-loaded. Every sentence contributes an actionable constraint, and the length is appropriate for a 23-parameter mutation tool.

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

Completeness5/5

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

Given the complex schema, mutation annotations, and absence of an output schema, the description supplies the missing operational context: patch semantics, side effects, prerequisite reading, sibling alternatives, and plan/target restrictions. It is complete enough for an agent to invoke the tool 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 description coverage is 100%, so the schema already documents each parameter in detail. The description still adds valuable cross-parameter semantics: at least one changed field is required, omitted fields are preserved, type is immutable, list/header inputs replace existing values, and null clears supported optional settings.

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?

The description opens with a specific verb and resource: 'Patch an existing monitor and return its updated record.' It clearly distinguishes this tool from related siblings such as get_monitor, pause_monitor, and resume_monitor.

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

Usage Guidelines5/5

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

It gives explicit workflow guidance: read get_monitor first, then send id and at least one changed field. It also names the alternatives, saying to prefer pause_monitor/resume_monitor for a pause-only change and use update_monitor for configuration changes or a combined edit.

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