delete_team
Delete a team and everything scoped to it. Owner only, irreversible.
Deletes a team. Only the owner may do it — destroying the container everyone else works in is not something a member can decide.
Irreversible, and it takes everything with it
A team is the tenant that projects, plans, subscriptions, roles and groups hang off. Deleting one is not a tidy-up; confirm with a human before calling this. The tool is annotated destructive so a client can prompt for confirmation.
Unlike create_team and update_team, this is not tier-gated. A creator
whose tier lapsed has to be able to take access away. See what the tier
gates.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it. It reaches beyond Subscriby: a connector, a provider or a member.
Arguments
team_id*stringUUID of the team to delete. Irreversible.
What it returns
{ "data": { "id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86", "deleted": true }}Emits team.deleted.
How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks team:delete.
RESOURCE_NOT_FOUNDno such team, or the caller is not a member.
VALIDATION_FAILEDthe caller is a member but not the owner.
How is this guide?
Last updated on