Skip to main content
Glama
arttus

umami-mcp-server

by arttus

Update an Umami user

umami_update_user
Idempotent

Update an existing Umami user's username, password, or instance-wide role. Requires admin access to manage account credentials and permissions.

Instructions

Change a login account's username, password, or instance-wide role.

Admin access required. Not available on Umami Cloud.

Args:

  • user_id (string, required): User UUID.

  • username (string, optional): New username.

  • password (string, optional): New password.

  • role ('admin' | 'user' | 'view-only', optional): New instance-wide role.

Returns: { "id": string, "username": string, "role": string }

Examples:

  • "Promote jordan to admin" -> user_id="...", role="admin"

  • "Reset their password" -> user_id="...", password=""

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoNew instance-wide role.
user_idYesUser UUID.
passwordNoNew password.
usernameNoNew username.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate a mutating, non-destructive, idempotent operation. The description adds important behavioral context beyond those hints: admin authorization is required, the tool is unavailable on Umami Cloud, and the response shape is disclosed. 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-structured with a summary, constraints, args, return type, and examples. It is slightly redundant with the input schema's parameter descriptions, but the layout is clean and front-loaded with the core purpose and access requirements.

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?

Despite having no output schema, the description states the exact return shape, required and optional parameters, role enum options, authorization requirement, and availability limitation. Examples further reduce ambiguity for natural-language requests, making it complete enough to invoke correctly.

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 parameters. The description echoes the same semantics and adds useful natural-language examples, but does not meaningfully expand on parameter meaning beyond what the schema provides.

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 opens with a specific verb and resource: 'Change a login account's username, password, or instance-wide role.' This clearly identifies the operation as an update to an existing user and distinguishes it from sibling create/delete/get user tools, as well as team-user updates.

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?

It provides explicit conditions: 'Admin access required' and 'Not available on Umami Cloud,' which tell an agent when the tool can be invoked. It does not explicitly name alternatives such as create_user or delete_user, but the update-focused wording sufficiently implies existing-account context.

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