update_team
Rename a team. Owner only, Growth-tier capability.
Renames a team. name is the only mutable field on a team — ownership does not transfer, and the tier a team sits on is a property of the owner's billing rather than of the team.
Only the owner may rename. Belonging to a team is enough to read it and to add to it; changing what everyone else's workspace is called is the owner's alone.
Growth-tier capability. On a lower tier this returns TEAM_TIER_REQUIRED and
changes nothing.
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 rename.
name*stringNew team name, 1..255 characters.
What it returns
{ "data": { "id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86", "name": "Research Collective", "owner_user_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80" }}Emits team.updated, which fires however the rename happened — this tool, the REST endpoint, or the dashboard.
How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks team:update.
TEAM_TIER_REQUIREDthe caller's platform tier does not include Teams.
RESOURCE_NOT_FOUNDno such team, or the caller is not a member. A team in another account is invisible rather than forbidden, so the tool cannot be used to discover that an id exists.
VALIDATION_FAILEDname empty or too long, or the caller is a member but not the owner.
How is this guide?
Last updated on