umami-mcp

update_team_user

Change a team member's role in an Umami team by specifying the team UUID, user UUID, and new role: team-member, team-view-only, or team-manager.

Instructions

Update a team member's role

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "teamId": "<teamId>",
      "userId": "<userId>",
      "role": "<role>"
    },
    "name": "update_team_user"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	New team role
`teamId`	Yes	Team UUID
`userId`	Yes	User UUID

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.1Oct 24, 2026
- changedInput schema / properties / role / description
```
Previous value: -"New role: 'team-owner' or 'team-member'"New value: +"New team role"
```
- addedInput schema / properties / role / enum
```
Added value: +[
+  "team-member",
+  "team-view-only",
+  "team-manager"
+]
```
- addedInput schema / properties / teamId / format
```
Added value: +"uuid"
```
- addedInput schema / properties / userId / format
```
Added value: +"uuid"
```
First observedv1.2.1Mar 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosure. It says nothing about permission requirements (admin/manager), whether the change is reversible, what happens to a demoted user's access, or what the response contains — all critical for a mutation tool.

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?

A single, front-loaded sentence with no waste; nothing is buried. It is terse to the point of under-specification, but every word earns its place.

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

Completeness2/5

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

The schema is complete and enum-constrained and there is no output schema, but for an unannotated mutation tool the description leaves out authorization context, side effects of role changes, and any notion of failure modes. It is barely adequate rather than complete.

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

Parameters3/5

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

Schema description coverage is 100%, with teamId/userId documented as UUIDs and role carrying an enum of team-member, team-view-only, team-manager, so the schema does the heavy lifting. The description confirms that only the role is being changed but adds no format or semantics beyond the schema.

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

Purpose4/5

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

The description gives a specific verb and resource ('Update a team member's role') and even narrows the scope to the role field, so the agent knows this is not a general member edit. It does not explicitly distinguish itself from siblings like update_team, update_user, or add_team_user, but the 'team member' + 'role' framing is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus add_team_user (to add), remove_team_user (to remove), or get_team_user (to inspect). No prerequisites such as required permissions or the fact that the user must already be a team member are stated.

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

Deploy Server