Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Update Metric Monitor

update_metric_monitor
Destructive

Modify an existing Sentry metric monitor's query, detection conditions, name, owner, status, or linked Alerts while preserving omitted fields.

Instructions

Update a Sentry Metric Monitor: its query, detection mode and conditions, name, owner, status, or connected Alerts. Omitted fields stay unchanged. Read it with get_metric_monitor_details first. Alert notification actions change with update_alert_rule. 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": "update_metric_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
ownerNoOwner as user:<id> or team:<id>. Null clears it.
queryNoQuery fields to change; omitted fields are kept and a null environment clears the filter. A new dataset needs a matching aggregate and eventTypes.
configNoDetection config fields to change. Static and Dynamic clear the comparison delta; a new detection type needs a matching condition group.
statusNo
monitorIdYesMetric Monitor ID from find_metric_monitors, not a legacy metric alert ID.
regionUrlNo
descriptionNo
projectSlugNoThe project slug. In `org/project` notation, the part after the slash.
workflowIdsNoAlert workflow IDs to connect; replaces the current list. Copy IDs to keep from get_metric_monitor_details; [] disconnects all. The Alerts are not edited.
conditionGroupNoReplaces all detection conditions; keep existing IDs. Static and Percent use threshold conditions, including a resolved one. Dynamic uses one anomaly_detection condition.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
monitorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructive, non-idempotent, and open-world behavior. The description adds that omitted fields stay unchanged, which is useful partial-update semantics, and routes alert notification actions away from this tool. However, it does not warn that condition groups and workflow IDs replace entire lists, or that connected Alerts themselves are not edited; with annotations carrying the safety profile, this is adequate but not rich.

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 front-loaded with the core action and scope, followed by a concise prerequisite and sibling-routing sentence. Every sentence is useful and there is no filler.

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 12-parameter nested mutation tool with output schema and safety annotations, the description covers the key prerequisite and sibling routing, plus partial-update behavior. It relies on the schema for replacement semantics and field-level detail, which is acceptable given schema richness, but it could mention replacement behavior more explicitly.

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 67%, and the description lists the main updatable surfaces, but it adds little meaning beyond the schema's property documentation. It states that omitted fields stay unchanged, yet the schema already says the same for query and config. Nested behavior and required context such as monitorId, regionUrl, organizationSlug, and projectSlug are left to the schema.

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 states a specific verb and resource ('Update a Sentry Metric Monitor') and enumerates the updatable aspects: query, detection mode and conditions, name, owner, status, and connected Alerts. It also separates this tool from adjacent resources by routing alert notification actions, cron jobs, and URL checks to their respective siblings.

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 an explicit prerequisite ('Read it with get_metric_monitor_details first') and names alternatives for adjacent operations ('Alert notification actions change with update_alert_rule', 'Cron jobs: find_monitors', 'URL checks: find_uptime_monitors'). The guidance clearly orients the agent before invocation.

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