umami-mcp

list_reports

Retrieve saved reports for a specific website, with optional filtering by report type and pagination. Use it to browse existing analytics reports before viewing or managing them.

Instructions

List saved reports for a website

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": {
      "websiteId": "<websiteId>"
    },
    "name": "list_reports"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`type`	No	Optional report type filter
`pageSize`	No	Results per page
`websiteId`	Yes	Website UUID

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.1Oct 24, 2026

removedInput schema / properties / orderBy

Removed value: -{
-  "description": "Field to order by",
-  "type": "string"
-}

addedInput schema / properties / type

Added value: +{
+  "description": "Optional report type filter",
+  "enum": [
+    "attribution",
+    "breakdown",
+    "funnel",
+    "goal",
+    "heatmap",
+    "journey",
+    "performance",
+    "retention",
+    "revenue",
+    "utm"
+  ],
+  "type": "string"
+}

addedInput schema / properties / websiteId

Added value: +{
+  "description": "Website UUID",
+  "format": "uuid",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "websiteId"
+]
```

First observedv1.2.1Mar 19, 2026

TDQS

B3.1/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 state that this is a read-only operation, nor does it disclose pagination behavior, default page size, ordering, or the shape of returned reports — all relevant for a list tool with four parameters.

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 no filler, and the resource is front-loaded. It is efficient but borders on under-specification rather than being genuinely well-structured.

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 and no output schema, the description should explain return values, pagination defaults, and read-only semantics. It says nothing about these, leaving the agent to guess at behavior for a four-parameter listing tool.

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 100%, so page, pageSize, type, and websiteId are all documented in the schema itself. The description adds only the website scoping hint already implied by the required websiteId parameter, so baseline 3 applies.

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 ('List saved reports') and scopes it to a website, which is clearly distinct from mutating siblings like create_report or delete_report. However, it does not differentiate itself from get_report, get_website_reports, or run_report, which an agent could easily confuse it with.

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 description implies a browsing/enumeration use case but gives no explicit guidance on when to use it versus get_report, get_website_reports, or run_report. No exclusions or prerequisites are stated, leaving usage 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