umami-mcp

list_team_users

Lists all members of a specified Umami Analytics team, with optional pagination and search filters to find team users.

Instructions

List all members of a team

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>"
    },
    "name": "list_team_users"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`search`	No	Search query to filter members
`teamId`	Yes	Team UUID
`pageSize`	No	Results per page

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 members",
-  "type": "string"
-}

addedInput schema / properties / search

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

addedInput schema / properties / teamId / 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?

With zero annotations, the description carries the full disclosure burden and provides almost none. Saying it lists 'all' members is mildly misleading given the page/pageSize pagination parameters, and it does not say whether this requires team membership or admin rights, nor what a member record contains.

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 filler. Its brevity is efficient but veers toward under-specification rather than tight information design.

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 four-parameter list tool with no annotations and no output schema needs the description to explain pagination behavior, filter semantics, and permission requirements. None of that is present, leaving the agent with less than a minimum viable definition.

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 coverage is 100%, so teamId, page, pageSize, and search are all self-documented. The description adds nothing about them and notably does not reconcile 'all members' with the paginated result set, so it earns only the 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?

States a specific verb and resource: list members of a team, with teamId required. This is clear enough to separate it from list_users and list_teams, though it does not explicitly contrast with near-siblings like get_user_teams or get_team_user.

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 when-to-use guidance, no mention of prerequisites (e.g. requiring a team UUID you already know), and no routing to alternatives such as list_users or get_user_teams for a user-centric view. The agent must infer everything from the name.

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

Deploy Server