Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Update DSN

update_dsn
DestructiveIdempotent

Modify a Sentry project's DSN client key by renaming it, enabling or disabling event intake, adjusting rate limits, or changing JavaScript Loader Script settings.

Instructions

Update a DSN (client key) on a Sentry project: rename it, activate or deactivate it, set or remove its rate limit, or change JavaScript Loader Script options. Returns the settings Sentry saved; tell the user if any requested setting did not change.

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>",
      "keyId": "<keyId>"
    },
    "name": "update_dsn"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew key name.
keyIdYesClient key ID from find_dsns.
isActiveNoFalse stops the key from accepting events.
regionUrlNo
projectSlugYesThe project slug. In `org/project` notation, the part after the slash.
loaderHasDebugNoLoader Script: use the debug bundle with SDK logging.
rateLimitCountNoMaximum events accepted per window. Requires rateLimitWindow.
loaderHasReplayNoLoader Script: enable Session Replay.
rateLimitWindowNoRate limit window in seconds. Requires rateLimitCount.
disableRateLimitNoTrue removes the rate limit. Do not combine with rateLimitWindow or rateLimitCount.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.
browserSdkVersionNoJavaScript SDK version the Loader Script serves, such as `latest` or `8.x`.
loaderHasFeedbackNoLoader Script: enable User Feedback.
loaderHasPerformanceNoLoader Script: enable tracing (performance monitoring).
loaderHasLogsAndMetricsNoLoader Script: enable logs and metrics. Requires SDK 10.0.0 or later.

Output Schema

NameRequiredDescriptionDefault
dsnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the destructive/open-world/idempotent profile, so the bar is lower, and the description still adds real value by disclosing that the tool returns the settings Sentry saved and that some requested settings may silently fail to apply. That partial-application behavior is not derivable from the annotations. It omits permission requirements and whether unspecified fields are left untouched, keeping it below 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, front-loaded with the action and its scope, followed by the return/side-effect caveat. Every clause carries information; nothing is redundant with the title or schema.

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 15-parameter mutation with an output schema and near-complete parameter documentation, the description covers purpose, scope, and the key reconciliation behavior. Minor gaps remain around permission requirements and confirming that only supplied fields are changed, but nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 93%, so the baseline is 3, but with 15 parameters the description earns extra credit by grouping the inputs into four coherent intents (naming, activation, rate limiting, Loader Script options), giving an agent a mental map before reading the schema. It adds no syntax or format detail beyond what the schema already supplies, which is appropriate here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update a DSN (client key) on a Sentry project') and enumerates the change categories: rename, activate/deactivate, rate limit, and Loader Script options. This makes it distinguishable from create_dsn and update_project by resource. It stops short of explicitly naming a sibling to avoid, so it is not quite a 5.

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?

Usage is implied rather than stated: an agent can infer this is the tool for modifying an existing client key, but there is no explicit when-to-use vs. when-to-use-an-alternative guidance and no prerequisites (e.g., that keyId should come from find_dsns). The closing instruction about telling the user when a setting did not change is result-handling guidance, not selection guidance.

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