umami-mcp

list_users

Retrieve all Umami users with admin-only access, using pagination, search filtering, and sorting to find and review user accounts.

Instructions

List all users (admin only)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_users"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`search`	No	Search query to filter users
`orderBy`	No	Field to order by (e.g. 'username', 'createdAt')
`pageSize`	No	Results per page (default 10)
`sortDescending`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.1.1Oct 24, 2026

removedInput schema / properties / query

Removed value: -{
-  "description": "Search query to filter users",
-  "type": "string"
-}

addedInput schema / properties / search

Added value: +{
+  "description": "Search query to filter users",
+  "type": "string"
+}

addedInput schema / properties / sortDescending
```
Added value: +{
+  "type": "boolean"
+}
```

First observedv1.2.1Mar 19, 2026

TDQS

A3.5/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 behavioral burden. It usefully discloses the admin-only authorization requirement, but it does not describe pagination behavior, return shape, or any side effects beyond the obvious read-only implication of 'list'.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no wasted words. The core action and key constraint are immediately visible.

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

Completeness3/5

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

The tool is simple and most parameter details are in the schema, but the description does not explain filtering, pagination, or expected output. For a user-listing endpoint with several optional filters, it is adequate but leaves some contextual gaps.

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 80%, so the schema already documents most parameters. The description adds no parameter-specific meaning, which meets the baseline for high schema coverage but does not compensate for the remaining gap.

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 ('List all users') and adds a meaningful scope/constraint ('admin only'). It is clear what the tool does, though it does not explicitly distinguish itself from siblings like list_team_users or get_user.

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 'admin only' note provides an important prerequisite, but there is no explicit guidance on when to use this tool versus get_user, list_team_users, or create_user. Usage is only implied by the name and scope.

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

Deploy Server