Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Delete Alert Rule

delete_alert_rule
DestructiveIdempotent

Permanently deletes a Sentry alert workflow and its notifications across every connected project and monitor; connected monitors remain intact.

Instructions

Permanently delete a Sentry Alert (notification workflow) and its notifications for every connected project and monitor. Connected monitors are kept. To stop one source or pause it, use update_alert_rule. Metric Monitors are deleted with delete_metric_monitor.

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": {
      "ruleId": "<ruleId>"
    },
    "name": "delete_alert_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleIdYesAlert workflow ID from get_alert_rule with `issue`. Metric Monitor and legacy metric alert IDs are not workflow IDs.
regionUrlNo
projectSlugNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
ruleIdYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds real context beyond that: the deletion is permanent and cascades to notifications across every connected project and monitor, while connected monitors survive. It does not mention permission requirements or confirmation behavior, which keeps it short of a 5.

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, zero filler. The destructive scope and the preservation caveat are front-loaded, and the sibling routing follows in the second sentence. Every clause carries information an agent needs.

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?

For a destructive, four-parameter mutation with an output schema and full annotation coverage, the definition covers blast radius, cascade behavior, and alternatives. What is missing is minor: no mention of required scoping context (org/region) or any permission precondition, but the schema supplies those parameter details.

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?

The description says nothing about ruleId, regionUrl, projectSlug, or organizationSlug. With schema description coverage at 50%, the schema does document the critical ruleId (including that metric monitor and legacy alert IDs are not workflow IDs), but the description adds no compensating meaning for the remaining parameters. Baseline 3 for partial coverage with the schema doing the heavy lifting.

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 gives a specific verb ('Permanently delete') and a precisely scoped resource ('a Sentry Alert (notification workflow) and its notifications for every connected project and monitor'), plus the explicit clarification that connected monitors are kept. It names the two siblings an agent might confuse it with (update_alert_rule, delete_metric_monitor), so the tool is separable without opening any schema.

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 supplies explicit when-not routing: 'To stop one source or pause it, use update_alert_rule' and 'Metric Monitors are deleted with delete_metric_monitor.' Both the alternative tool and the condition that selects it are stated, leaving nothing to inference about the adjacent cases.

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