umami-mcp

list_teams

Retrieve all Umami teams with pagination, ordering, and sort direction controls to browse team management data.

Instructions

List all teams

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_teams"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.1Oct 24, 2026

removedInput schema / properties / query

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

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

First observedv1.2.1Mar 19, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses nothing about permissions required, whether results are scoped to the caller's memberships, or how pagination behaves. Only the implicit read-only nature of "List" is conveyed.

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

Conciseness3/5

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

Three words with zero waste, but this is under-specification rather than conciseness: a paginated, sortable listing tool needs at least a scope statement, and none is present to be front-loaded.

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?

With no annotations, no output schema, and four parameters, the description should establish result scope and return shape. It establishes neither, leaving the agent unable to predict what a call returns or whether pagination must be driven manually.

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 75%, so page, orderBy, and pageSize are already documented in the schema. The description mentions none of the four parameters and adds no sorting or pagination semantics, so it neither helps nor compensates for the undocumented sortDescending flag.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List all teams" gives a clear verb and resource, but it adds nothing beyond the tool name and leaves "all" ambiguous: all teams in the account, all teams visible to the caller, or all teams across the organization. With siblings like get_my_teams, list_admin_teams, and get_user_teams present, that ambiguity matters and no differentiation is offered.

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 guidance on when to use this rather than get_my_teams, list_admin_teams, or get_user_teams, nor any stated prerequisites such as admin rights or team membership. The agent must infer selection from the name alone.

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

Deploy Server