Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Update Project

update_project
Destructive

Rename a Sentry project, change its slug, or update its platform, then return the updated project.

Instructions

Rename a Sentry project, change its slug, or change its platform. Returns the updated project. To change which teams can access a project, use add_team_to_project or remove_team_from_project.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
slugNo
platformNo
regionUrlNo
projectSlugYesThe 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
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds only that the updated project is returned and that team access is out of scope; it does not mention that a slug change can break existing integrations or that omitted fields are left untouched, which would be genuinely valuable for a destructive mutation.

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 short sentences with no waste: the mutation scope is front-loaded and the sibling redirect follows. Every clause earns its place.

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, so return-value detail is not required, and the destructive semantics are covered by annotations. The remaining gap is the undocumented organizationSlug/regionUrl context, which matters for a mutation that can move a project to a new slug.

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 only 33%, so the description carries partial burden. It does enumerate the three user-facing mutable fields (name, slug, platform), which maps to real parameters, but says nothing about organizationSlug or regionUrl, which are needed for correct invocation in multi-region or multi-org setups.

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 names specific verbs and resources: rename, change slug, change platform on a Sentry project, and states it returns the updated project. It also explicitly separates this tool from the team-access siblings, so an agent can distinguish it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete routing rule for a closely related task: team access changes belong to add_team_to_project or remove_team_from_project. It does not cover when to use this versus other update_* tools, but the guidance present is explicit and actionable.

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