umami-mcp

get_my_websites

Retrieve the list of websites owned by the current Umami user, with pagination, sorting, and optional inclusion of team-accessible websites.

Instructions

Get the list of websites belonging to the current user

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": "get_my_websites"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`orderBy`	No	Sort field
`pageSize`	No	Results per page
`includeTeams`	No	Include team-accessible websites
`sortDescending`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.1Oct 24, 2026

addedInput schema / properties / includeTeams

Added value: +{
+  "description": "Include team-accessible websites",
+  "type": "boolean"
+}

addedInput schema / properties / orderBy

Added value: +{
+  "description": "Sort field",
+  "type": "string"
+}

removedInput schema / properties / query

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

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

First observedv1.2.1Mar 19, 2026

TDQS

C2.6/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. It does not disclose pagination behavior, default sort order, whether team sites are included by default, or anything about permissions/authorship scope beyond 'belonging to the current user'.

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 that front-loads the resource and scope. It is efficient, though its brevity comes at the cost of the missing guidance noted elsewhere.

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 five parameters, pagination and an includeTeams flag, and no output schema, the description should explain the return shape, default inclusion of team sites, and how pagination interacts with results. It covers none of that.

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 80%, with page, orderBy, pageSize, and includeTeams documented in the schema; sortDescending has no description. The description adds no parameter guidance at all, so it merely meets the baseline when the schema does the work.

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?

States a specific verb and resource (get the list of websites) scoped to the current user, which is somewhat distinguishing. However, siblings like list_websites and get_user_websites plausibly do the same thing, and the description offers no differentiation between them.

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 statement of when to use this tool versus list_websites, get_user_websites, or get_website. The agent must infer the distinction, and the 'current user' scoping is the only hint.

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

Deploy Server