umami-mcp

update_user

Update a user's username, password, or role (admin only) to manage Umami Analytics account credentials and access permissions.

Instructions

Update a user's username, password, or role (admin only)

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": {
      "userId": "<userId>"
    },
    "name": "update_user"
  }
}

Input Schema

Name	Required	Description
`role`	No	New role
`userId`	Yes	User UUID
`password`	No	New password
`username`	No	New username

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.1.1Oct 24, 2026
- addedInput schema / properties / password / maxLength
```
Added value: +255
```
- addedInput schema / properties / password / minLength
```
Added value: +8
```
- changedInput schema / properties / role / description
```
Previous value: -"New role: 'admin' or 'user'"New value: +"New role"
```
- addedInput schema / properties / role / enum
```
Added value: +[
+  "admin",
+  "user",
+  "view-only"
+]
```
- addedInput schema / properties / userId / format
```
Added value: +"uuid"
```
- addedInput schema / properties / username / maxLength
```
Added value: +255
```
First observedv1.2.1Mar 19, 2026

TDQS

B3.1/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 behavioral disclosure. It mentions an admin restriction, which is useful, but does not clarify whether that restriction applies to role changes only, whether username/password changes are self-service, whether changes are reversible, or what happens on validation failure.

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 a single, front-loaded sentence with no wasted text. The ambiguous placement of '(admin only)' is the main structural weakness, but overall it is appropriately sized.

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?

For a mutation tool with no annotations and no output schema, the description is too sparse. It does not explain permission requirements clearly, side effects, whether self-update is allowed, or expected outcomes, leaving an agent with significant gaps before calling it safely.

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%, so the schema already documents all four parameters including the role enum and string constraints. The description adds only a high-level list of fields and no additional syntax, format, or behavioral detail beyond the schema baseline.

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 states a specific verb and resource ('Update a user') and enumerates the editable fields (username, password, role), so the tool's purpose is immediately clear. It does not explicitly differentiate itself from nearby tools like update_my_password or update_team_user, which keeps it from a 5.

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

Usage Guidelines3/5

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

The parenthetical '(admin only)' gives some usage guidance, but it is ambiguous whether the entire tool is admin-restricted or only the role update is. There is no explicit guidance on when to use this instead of update_my_password or update_team_user.

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

Deploy Server