remove_team_member
Remove a collaborator from a team. Their Subscriby account is untouched.
Removes a collaborator from a team. They lose access to every project and setting scoped to it immediately; their own Subscriby account is untouched.
The team owner cannot be removed — ownership is not a membership row.
Not tier-gated, unlike inviting. A creator whose tier lapsed with collaborators still attached has to be able to remove them; gating that would turn a downgrade into a permanent grant. See what the tier gates.
Only works on someone who has accepted. Somebody still holding an
unaccepted invitation has no membership row to remove — use
cancel_team_invitation for those. Using
the wrong one returns RESOURCE_NOT_FOUND rather than doing something
surprising.
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.
user_id*stringUUID of the collaborator to remove.
What it returns
{ "data": { "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86", "user_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80", "removed": true }}Emits team.member.removed.
How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks team-member:remove.
RESOURCE_NOT_FOUNDno such team, or user_id is not a member. The owner also returns 404.
How is this guide?
Last updated on