umami-mcp

get_event_data_events

Retrieve custom event names and counts for a website within a specified time range, with optional event-name and additional filters. Use it to analyze which Umami events occur and how often.

Instructions

Get event data events (custom event names and counts) 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>",
      "startAt": "<startAt>",
      "endAt": "<endAt>"
    },
    "name": "get_event_data_events"
  }
}

Input Schema

Name	Required	Description
`endAt`	Yes	End timestamp in milliseconds
`event`	No	Filter by event name
`filters`	No	Additional current Umami filter fields
`startAt`	Yes	Start timestamp in milliseconds
`websiteId`	Yes	Website UUID

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.1.1Oct 24, 2026

addedInput schema / properties / event

Added value: +{
+  "description": "Filter by event name",
+  "type": "string"
+}

removedInput schema / properties / eventName

Removed value: -{
-  "description": "Filter by event name",
-  "type": "string"
-}

addedInput schema / properties / filters

Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  "description": "Additional current Umami filter fields",
+  "type": "object"
+}

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. 'Get' implies a read, but the description says nothing about aggregation behavior, whether counts are scoped to the date range, rate limits, permissions, or result shape for what appears to be a time-bounded analytics query.

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 compact sentence, front-loaded with the verb and resource, with the parenthetical clarification placed immediately. The phrase 'event data events' is slightly redundant but the sentence earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, schema-complete query tool with no output schema, the description is minimally sufficient to attempt a call. It falls short of being complete given the dense cluster of event siblings that require differentiation for reliable selection.

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 all five parameters (websiteId, startAt, endAt, event, filters) are documented in the schema itself. The description adds no syntax, defaults, or semantics for the nested 'filters' object beyond what the schema states, so baseline 3 applies.

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?

The description states a verb ('Get') and a resource ('event data events'), and the parenthetical narrows it to custom event names and counts for a website. However, it does not distinguish this from closely related siblings like get_events, get_event_data_fields, get_event_data_values, or get_event_data_stats, so an agent must guess which event query to select.

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 prerequisites, and no mention of alternatives among the many event-related siblings. The 'for a website' phrase hints at context but does not route the agent.

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

Deploy Server