Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Remove Team from Project

remove_team_from_project
Destructive

Revoke a team's access to a Sentry project and return the project's remaining teams. Refuses to remove the project's last team.

Instructions

Revoke a team's access to a Sentry project. Returns the project's remaining teams. Refuses to remove the project's last team.

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

Input Schema

NameRequiredDescriptionDefault
teamSlugYesThe team slug.
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
teamsYes
changedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. The description still adds real value beyond them: it discloses the return payload (remaining teams) and a non-obvious failure mode (refusal when removing the last team), which an agent must anticipate. It stops short of stating whether the removal is reversible or what error/result shape the refusal produces.

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?

Three short sentences, front-loaded with the action, then the return value, then the guardrail. Nothing is wasted and each sentence carries distinct information.

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 mutation with an output schema present, the description supplies the essential behavioural guardrail and the return payload, and the schema carries parameter detail. Only the authorization/permanence aspects are left unstated, a minor gap against the annotation coverage.

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 75% and all four parameters carry their own descriptions, including the regionUrl and org/project notation hints. The description mentions no parameters and adds no meaning beyond the schema, so the baseline 3 applies.

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: 'Revoke a team's access to a Sentry project.' That is clearly distinct from the sibling add_team_to_project by polarity, though the description never names the counterpart explicitly, so differentiation rests on the verb choice alone.

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?

The 'Refuses to remove the project's last team' clause is a useful precondition, but there is no explicit when-to-use guidance, no naming of alternatives (e.g., add_team_to_project, update_project), and no statement about required permissions or scopes. Usage is only implied by the verb.

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