Skip to main content
Glama
arttus

umami-mcp-server

by arttus

Add a user to a team

umami_add_team_user

Add an existing Umami user to a team directly by user ID, bypassing the access code. Assign their role as manager, member, or view-only with appropriate team permissions.

Instructions

Add an existing Umami login to a team directly, without needing the access code. Requires team-manager or owner permission on the team.

Args:

  • team_id (string, required): Team UUID.

  • user_id (string, required): User UUID to add. Get this from umami_list_users.

  • role ('team-manager' | 'team-member' | 'team-view-only'): Role within the team (default: 'team-member').

Returns: { "team_id": string, "user_id": string, "role": string }

Examples:

  • "Add jordan to the Gradeline team as a manager" -> team_id="...", user_id="...", role="team-manager"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoRole within the team.team-member
team_idYesTeam UUID.
user_idYesUser UUID to add.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already convey this is a non-read-only, non-destructive, non-idempotent operation. The description adds meaningful behavioral context: it performs a direct membership add, requires elevated permission, and bypasses the normal access-code requirement. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with Args/Returns/Examples sections, front-loads the purpose, and avoids unnecessary filler. Slight redundancy with the schema's parameter descriptions, but the example earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description explicitly defines the return shape. Permission requirements, parameter sourcing, role defaults, and an example are all present. An agent has everything needed to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by telling the agent to get user_id from umami_list_users and provides a concrete example mapping natural language to role values, plus the default role is restated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Add'), resource ('an existing Umami login to a team'), and the key differentiator ('directly, without needing the access code'), which clearly distinguishes it from the sibling umami_join_team. The permission requirement is also stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'without needing the access code' signals when this tool is appropriate versus the access-code flow, and the permission requirement ('team-manager or owner permission') gives an explicit gate. It does not name the alternative tool directly, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.