list_roles
List roles across every team the caller owns or belongs to. Each role carries a flat permission list and whether it was seeded.
List roles across every team the caller owns or belongs to. Each role carries a flat permissions array, the same entity:action strings a token would use, and seeded, which marks the eight roles every team starts with (admin, project_manager, business_analyst, developer, qa_engineer, release_manager, viewer, guest) apart from the ones the owner added. Read-only; roles are edited in the application.
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.
Annotations
It reads and never changes anything.
Arguments
This tool takes no arguments.
What it returns
{ "data": [ { "id": "d05e1a83-7c46-4f29-b613-8ae407c9d251", "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86", "code": "developer", "name": "Developer", "description": "Builds against the backlog and the board, reads the planning record and executes tests.", "seeded": true, "permissions": ["project:view-any", "project:view", "activity:read"] } ], "meta": { "total": 8 }}How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks role:view-any.
How is this guide?
Last updated on