Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Delete Metric Monitor

delete_metric_monitor
DestructiveIdempotent

Permanently delete a Sentry Metric Monitor along with its legacy metric alert and incident history, while keeping connected alerts intact.

Instructions

Permanently delete a Sentry Metric Monitor, and its legacy metric alert and incident history if present. Connected Alerts are kept. To pause detection instead, use update_metric_monitor. Cron jobs: find_monitors. URL checks: find_uptime_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": {
      "monitorId": "<monitorId>"
    },
    "name": "delete_metric_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitorIdYesMetric Monitor ID from find_metric_monitors, not a legacy metric alert ID.
regionUrlNo
projectSlugNoThe project slug. In `org/project` notation, the part after the slash.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
successYes
monitorIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, but the description still earns credit by naming the exact cascade (legacy metric alert and incident history) and what is explicitly preserved (Connected Alerts). Permanence is stated up front, which is the single most important behavioral fact for a delete tool.

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?

Two sentences, both front-loaded: the destructive scope first, the escape hatches second. No preamble, no restatement of the title, and every clause carries new information.

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?

Output schema and annotations cover the return shape and safety profile, so the description only needs to cover destruction scope and routing, which it does fully. For a 4-parameter destructive tool this leaves no decision-relevant gap.

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 coverage is 75% and the schema itself already carries the key semantic warning that monitorId is a metric monitor ID, not a legacy metric alert ID. The description adds no syntax, format, or constraint detail beyond that, so the baseline 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?

States a specific verb and resource ('Permanently delete a Sentry Metric Monitor') and immediately delimits the blast radius: legacy metric alert and incident history go, Connected Alerts stay. The schema's 'not a legacy metric alert ID' warning plus the sibling set makes it distinguishable from delete_alert_rule and delete_uptime_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?

Gives an explicit alternative with its condition ('To pause detection instead, use update_metric_monitor') and redirects the adjacent resource types to the correct discovery tools (find_monitors for cron jobs, find_uptime_monitors for URL checks). This is exactly the when-to-use-this-vs-something-else guidance that prevents a wrong deletion.

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