update_team

Purpose

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.

Required ability

team:update

Input schema

{
  "type": "object",
  "properties": {
    "team_id": {
      "type": "string",
      "description": "UUID of the team to rename."
    },
    "name": {
      "type": "string",
      "description": "New team name, 1..255 characters."
    }
  },
  "required": ["team_id", "name"]
}

Output shape

{
  "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.

Example prompts

"Rename my Research team to Research Collective."

Failure modes

AUTHENTICATION_REQUIRED — no authenticated user on the request.
TOKEN_MISSING_ABILITY — token lacks team:update.
TEAM_TIER_REQUIRED — the caller's platform tier does not include Teams.
RESOURCE_NOT_FOUND — no 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_FAILED — name empty or too long, or the caller is a member but not the owner.