umami-mcp

get_user_teams

Retrieve the teams a specified user belongs to; use this admin-only query to review team membership with optional pagination and sorting.

Instructions

Get the list of teams a user belongs to (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": "get_user_teams"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`userId`	Yes	User UUID
`orderBy`	No
`pageSize`	No	Results per page
`sortDescending`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.1Oct 24, 2026
- addedInput schema / properties / orderBy
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / query
```
Removed value: -{
-  "description": "Search query to filter teams",
-  "type": "string"
-}
```
- addedInput schema / properties / sortDescending
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / userId / format
```
Added value: +"uuid"
```
First observedv1.2.1Mar 19, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the admin-only access requirement, which is meaningful behavioral context. It says nothing about pagination defaults, ordering behavior, or whether a partial page indicates more results, all of which matter for a 5-parameter listing call.

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 short sentence with the key scope and the admin constraint front-loaded; nothing is wasted, though it is arguably too terse for the schema's complexity.

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 paginated, five-parameter listing tool with no annotations and no output schema, the description omits pagination behavior, ordering defaults, and return shape. The admin-only note is the only substantive addition beyond the name.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 60% schema description coverage and five parameters, orderBy and sortDescending are undocumented in both schema and description, and the description adds no meaning about userId format or pagination semantics. It does not compensate for the coverage 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?

States a specific verb and resource ('Get the list of teams a user belongs to') and scopes it to a single user, which implicitly distinguishes it from get_my_teams. However, it never names the sibling it is not, so an agent must infer the difference from the parameter list.

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)' qualifier gives a real precondition for use, but there is no explicit guidance on when to choose this over get_my_teams when inspecting one's own teams, and no exclusion or alternative is named.

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

Deploy Server