Version
DESTRUCTIVE

cancel_team_invitation

Withdraw a team invitation that has not been accepted.

Withdraws a pending invitation. The link stops working and the invitee never becomes a member.

An invitee is not a member

Someone who has not accepted has no membership row — only a pending invitation. That is why this is a separate tool from remove_team_member: the two fail on different things, and using the wrong one returns RESOURCE_NOT_FOUND instead of doing something surprising.

Not tier-gated. 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.

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

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

team_id*string

UUID of the team.

invitation_id*string

UUID of the pending invitation to withdraw.

What it returns

{  "data": {    "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86",    "invitation_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",    "cancelled": true  }}

No webhook event fires. An invitation that was never accepted changed nobody's access, so there is no membership transition to announce.

How it fails

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks team-member:remove.

RESOURCE_NOT_FOUND

no such team, or no pending invitation with that id on it. An invitation that has already been accepted is gone from this list; remove the member instead.

How is this guide?

Last updated on