Skip to main content
Glama
Sign In
umami-mcp

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_event_data_values

Retrieves aggregated counts for a specified property across website events within a time range, with optional event and filter criteria.

Instructions

Get event data values (aggregated counts for a specific property) 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>",
      "propertyName": "<propertyName>"
    },
    "name": "get_event_data_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
endAtYesEnd timestamp in milliseconds
filtersNoAdditional current Umami filter fields
startAtYesStart timestamp in milliseconds
dataTypeNoOptional Umami data type code
eventNameNoFilter by event name
websiteIdYesWebsite UUID
propertyNameYesProperty name to aggregate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.1
    • addedInput schema / properties / dataType
      Added value: +{
+  "description": "Optional Umami data type code",
+  "type": "integer"
+}
    • addedInput schema / properties / filters
      Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  "description": "Additional current Umami filter fields",
+  "type": "object"
+}
    • changedInput schema / properties / propertyName / description
      Previous value: -"Filter by property name"New value: +"Property name to aggregate"
    • changedInput schema / required
      Previous value: -[
-  "websiteId",
-  "startAt",
-  "endAt"
-]New value: +[
+  "websiteId",
+  "startAt",
+  "endAt",
+  "propertyName"
+]
  2. First observedv1.2.1

TDQS

C2.9/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 disclosure burden, yet it says nothing about authorization requirements, pagination, result ordering, limits, or what happens with an empty property. It only implies a read/aggregate operation, which is the minimum an agent could guess from the name.

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 no filler; the parenthetical clarification earns its place. It is efficient but perhaps too terse given the tool's 7-parameter surface.

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 7-parameter tool with a nested free-form 'filters' object, a raw Umami 'dataType' code, no annotations, and no output schema, the description is far too thin. An agent gets no help on filter key naming, timestamp semantics, or the shape of the returned counts.

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% with all 7 parameters documented, so the baseline is 3. The description reinforces that the aggregation is scoped by 'website' and 'specific property', but adds no syntax or semantics for filters, dataType, or eventName beyond what the schema already states.

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 event data values') and disambiguates the payload with a parenthetical ('aggregated counts for a specific property'), which is more informative than the name alone. However, it never distinguishes itself from close siblings like get_event_values, get_event_data_properties, get_event_data_fields, or get_session_data_values, so the agent still has to guess which one to pick.

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 the many adjacent event-data tools, and no prerequisites or exclusions. The only implicit signal is 'aggregated counts', which a reader must infer selects this over the raw-listing siblings.

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

Deploy Server

Other Tools