Skip to main content
Teams group users in Attention and control which calls, scorecards, and labels apply to them. Teams can be nested arbitrarily — every team has an optional parent, and the read tools return the full hierarchy. Read tools (list_teams, get_team, get_team_members) require only mcp:read. All write tools require mcp:write plus the admin role.

​
Read tools

​
list_teams

Scope: mcp:read. No parameters.
List all teams in your organization with their structure and sub-teams. Returns: A Markdown tree of teams with IDs, names, and parent relationships. Example prompt: “What teams do we have in Attention?“

​
get_team

Scope: mcp:read.
Get details about a specific team, including its sub-teams. Use the team ID from list_teams.
​
id
string
required
The team ID.
Returns: Team details (name, parent team, sub-teams).

​
get_team_members

Scope: mcp:read.
List all members of a specific team — names, emails, and roles.
​
id
string
required
The team ID.
Returns: Markdown list of team members with names, emails, and roles.

​
Write tools

​
create_team

Scope: mcp:write. Requires admin role.
Create a new team in your organization. Teams organize users and control which calls, scorecards, and labels apply to them.
​
name
string
required
The team name. Will be prefixed with the organization name automatically (e.g. Sales becomes [Acme Corp] Sales).
​
parent_team_id
string
UUID of the parent team. Omit for a top-level team. Use list_teams to find team IDs.
Returns: ID, name, and parent team of the newly created team.

​
update_team

Scope: mcp:write. Requires admin role.
Update a team’s name or parent team. Omitted fields preserve their current values.
​
team_id
string
required
The UUID of the team to update.
​
name
string
New team name.
​
parent_team_id
string
New parent team UUID. Use list_teams to find team IDs.

​
archive_team

Scope: mcp:write. Requires admin role.
Archive or unarchive a team. Archived teams are hidden from most views but their data is preserved — this is reversible.
​
team_id
string
required
The UUID of the team.
​
archived
boolean
required
Set to true to archive, false to unarchive.

​
change_team_parent

Scope: mcp:write. Requires admin role.
Move a team under a different parent team, or make it top-level by omitting parent_team_id. Use list_teams to see the current hierarchy.
​
team_id
string
required
UUID of the team to move.
​
parent_team_id
string
UUID of the new parent team. Omit to make the team top-level.

​
add_team_member

Scope: mcp:write. Requires admin role.
Add a user to a team. Provide either user_id or user_email.
​
team_id
string
required
The UUID of the team to add the member to.
​
user_id
string
UUID of the user to add. Provide either user_id or user_email.
​
user_email
string
Email of the user to add. Provide either user_id or user_email.
​
role_id
string
UUID of the role to assign. If omitted, the user’s default role is used. Use list_roles to find role IDs.
​
primary_team
boolean
Whether this should be the user’s primary team.

​
remove_team_member

Scope: mcp:write. Requires admin role.
Remove a user from a team. Use get_team_members to find user IDs.
​
team_id
string
required
The UUID of the team.
​
user_id
string
required
UUID of the user to remove from the team.