umami-mcp

get_user_websites

Retrieve the list of websites a user can access (admin only), with optional search, paging, ordering, and team inclusion.

Instructions

Get the list of websites a user has access 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_websites"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.1.1Oct 24, 2026

addedInput schema / properties / includeTeams
```
Added value: +{
+  "type": "boolean"
+}
```
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 / 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 are provided, so the description carries the full burden. It does disclose the meaningful behavioral constraint (admin-only access), but says nothing about what is returned, whether results are paginated by default, or how ordering behaves — gaps an agent must discover at call time.

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 access restriction front-loaded and no filler. It is efficiently written, though the brevity is partly a symptom of under-specification rather than discipline.

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 7-parameter admin tool with no annotations, no output schema, and less than 60% parameter coverage needs more than one sentence. Missing are return shape, pagination defaults, and how includeTeams or orderBy affect results.

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?

Seven parameters with only 57% schema coverage; the description explains none of them. The undocumented parameters (orderBy, includeTeams, sortDescending) get no clarification anywhere, and even for documented ones the description adds no meaning beyond the schema.

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 websites a user has access to') with the access-scope qualifier 'a user', which implicitly separates it from get_my_websites and list_websites. It does not name those siblings outright, so an agent must infer the distinction, but the purpose itself is unambiguous.

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?

'(admin only)' gives a real usage condition — the caller must hold admin privileges. However, it never names alternatives such as get_my_websites (for the caller's own sites) or list_admin_websites, so the routing decision between these near-identical siblings is left to inference.

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

Deploy Server