umami-mcp

list_team_websites

Retrieve websites that belong to a specific team, with optional pagination, search filtering, and sorting. Use it to inspect or manage a team's tracked sites in Umami.

Instructions

List all websites that belong to 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_websites"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

addedInput schema / properties / search

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

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

First observedv1.2.1Mar 19, 2026

TDQS

C2.7/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 says nothing beyond the bare purpose. It does not disclose pagination behavior, default page size, sort defaults, permission requirements, or what the response contains for a team with no websites.

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 zero redundancy or filler. Brevity here reflects under-specification rather than bloat, but the sentence itself is well-formed.

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 six-parameter tool with no annotations and no output schema, the description leaves an agent without enough to call it confidently: pagination contract, ordering semantics, and return shape are all undefined anywhere else.

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?

Schema coverage is 67% and the description mentions none of the six parameters, including the required teamId. The two undocumented parameters (orderBy, sortDescending) and the meaning of page/pageSize default behavior are left entirely to the schema, with no compensating detail.

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 (list) and a specific resource scope (websites belonging to a team), which is clearly distinct from list_websites and get_website. It stops short of naming which sibling to use for other scopes, so an agent must infer the contrast.

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. team membership or admin role), and no exclusions against the large set of sibling listers (list_websites, get_my_websites, list_admin_websites). The only cue is the tool name itself.

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

Deploy Server