umami-mcp

create_user

Create a new Umami Analytics user with a username, password, and role; restricted to admins for controlled team access.

Instructions

Create a new user (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": {
      "username": "<username>",
      "password": "<password>",
      "role": "<role>"
    },
    "name": "create_user"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	User role
`password`	Yes	Password for the new user
`username`	Yes	Username for the new user

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: -"User role: 'admin' or 'user' (default: 'user')"New value: +"User role"
```
- addedInput schema / properties / role / enum
```
Added value: +[
+  "admin",
+  "user",
+  "view-only"
+]
```
- addedInput schema / properties / username / maxLength
```
Added value: +255
```
- changedInput schema / required
```
Previous value: -[
-  "username",
-  "password"
-]New value: +[
+  "username",
+  "password",
+  "role"
+]
```
First observedv1.2.1Mar 19, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description must carry the safety profile, and it does disclose the key authorization constraint (admin only) for a mutation. It stops short of stating side effects, duplicate-username handling, whether the role is freely assignable, or what the call returns.

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?

Six words, zero filler, and the permission constraint is front-loaded. It is efficient but arguably thinner than a mutation tool warrants, which is captured under contextual completeness rather than here.

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?

A mutation tool with no annotations and no output schema requires the description to explain outcomes, error cases, and side effects. Aside from the admin-only note, none of that is present, leaving real gaps for an agent to call 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%: username, password (8-255 chars), and role (with an enum) are all documented in the schema. The description contributes nothing about parameter meaning or constraints, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a new user'), which cleanly separates it from sibling operations like update_user, delete_user, and list_users. No explicit sibling naming, but the verb makes the distinction obvious.

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)' signals a permission prerequisite for use, which is genuine guidance. However, there is no statement of when to prefer this over alternatives such as add_team_user, nor any exclusion or precondition beyond the admin requirement.

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

Deploy Server