Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Update Uptime Monitor

update_uptime_monitor
DestructiveIdempotent

Update a Sentry uptime monitor's URL, schedule, request settings, status, owner, environment, or failure thresholds while leaving omitted fields unchanged.

Instructions

Update a Sentry uptime monitor: URL, interval, timeout, HTTP method, headers, body, status, owner, environment, or failure thresholds. Omitted fields stay unchanged. Scheduled jobs (cron): find_monitors. Metric thresholds: find_metric_monitors.

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": {
      "projectSlug": "<projectSlug>",
      "uptimeMonitorId": "<uptimeMonitorId>"
    },
    "name": "update_uptime_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
bodyNoRequest body. Null clears it.
nameNo
ownerNoOwner as `user:ID` or `team:ID`. Null clears it.
methodNoHTTP method used for the uptime check request.
statusNoMonitor status. `disabled` stops checks and does not count against quota.
headersNoHTTP headers as [name, value] pairs, e.g. [["Accept","application/json"]].
regionUrlNo
timeoutMsNoRequest timeout in milliseconds.
environmentNoEnvironment name. Null clears it.
projectSlugYesThe project slug. In `org/project` notation, the part after the slash.
traceSamplingNo
intervalSecondsNoSeconds between checks: 60, 300, 600, 1200, 1800, or 3600.
uptimeMonitorIdYesUptime monitor ID from find_uptime_monitors.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.
downtimeThresholdNo
recoveryThresholdNo
responseCaptureEnabledNo

Output Schema

NameRequiredDescriptionDefault
monitorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely carried structurally. The description does add the partial-update contract ('Omitted fields stay unchanged'), which is useful and consistent with idempotentHint, but it never warns that this is a destructive mutation or that null-valued fields clear existing configuration, leaving the destructive hint unexplained.

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?

Two short sentences: the first front-loads the action and the mutable fields, the second states the partial-update rule, with routing notes last. Nothing is padded, though the trailing routing fragments are compressed enough to read as notes rather than guidance.

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?

An output schema exists, so return values need no explanation, and 16 of the 18 parameters are optional. Still, for a destructive 18-parameter mutation the description leaves threshold behavior, unmentioned parameters like regionUrl/traceSampling/responseCaptureEnabled, and the clearing semantics of nullable fields to the schema, which it only partially covers.

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 description coverage is 61%, so the schema does substantial work, including enums for method and status, the intervalSeconds allowed values, and null-clears notes. The description groups fields into readable clusters but adds no format, constraint, or interaction detail beyond what the schema already states, so it sits at the neutral baseline.

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 ('Update a Sentry uptime monitor') and immediately enumerates the mutable surface (URL, interval, timeout, method, headers, body, status, owner, environment, thresholds). That distinguishes it cleanly from create_uptime_monitor, delete_uptime_monitor, and update_metric_monitor without needing the schema.

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?

The closing lines route cron monitors to find_monitors and metric thresholds to find_metric_monitors, which is real guidance, and 'Omitted fields stay unchanged' implies partial-update usage. But there is no explicit statement about when to choose this versus create/update variants, and the routing fragments are terse enough that an agent must infer the exclusions.

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