Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Delete Uptime Monitor

delete_uptime_monitor
DestructiveIdempotent

Permanently delete a Sentry uptime monitor for an HTTP URL check. To pause a monitor instead of removing it, use the update action.

Instructions

Permanently delete a Sentry uptime (HTTP URL check) monitor. To pause it, use update_uptime_monitor. 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": "delete_uptime_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionUrlNo
projectSlugYesThe project slug. In `org/project` notation, the part after the slash.
uptimeMonitorIdYesUptime monitor ID from find_uptime_monitors.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
successYes
projectSlugYes
uptimeMonitorIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is known. The description adds only the word "Permanently," and says nothing about permissions required, whether dependent alert rules are affected, or whether deletion can be undone.

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 lines with the destructive scope front-loaded and the alternative immediately after; no waste. The trailing redirect note ("Scheduled jobs (cron): find_monitors") is terse to the point of being cryptic but still short.

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?

An output schema exists and annotations cover the destructive/idempotent profile, so the description needn't explain returns. It is nearly complete for a delete tool, with only permission and cascade consequences left implicit.

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?

All four parameters carry schema descriptions (75% coverage) and already point at find_organizations and find_uptime_monitors for sourcing values. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

"Permanently delete a Sentry uptime (HTTP URL check) monitor" gives a specific verb, resource, and even the resource's meaning (HTTP URL check), which separates it from cron monitors and metric monitors named in the same description.

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 explicitly routes the agent away from this tool when the intent is to pause ("use update_uptime_monitor") and names find_monitors / find_metric_monitors for the adjacent resource types, so wrong-tool selection is largely prevented.

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