Version
DESTRUCTIVE

delete_role

Delete a role. Collaborators holding it stay in the team.

Deletes a role. Anyone holding it stays in the team but loses whatever the role granted.

Not tier-gated, unlike creating and updating. 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

DestructiveOpen world

A client that honours annotations asks a person before running it. It reaches beyond Subscriby: a connector, a provider or a member.

Arguments

role_id*string

UUID of the role to delete. Irreversible.

What it returns

{  "data": {    "id": "d05e1a83-7c46-4f29-b613-8ae407c9d251",    "deleted": true  }}

How it fails

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks role:delete.

RESOURCE_NOT_FOUND

no such role in any team the caller belongs to.

How is this guide?

Last updated on