Skip to main content
Glama
Sign In
umami-mcp

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_event_values

Retrieve event or session property values for a website within a time range to analyze analytics breakdowns by dimensions such as path, referrer, browser, device, or UTM source.

Instructions

Get event or session property values 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>",
      "type": "<type>"
    },
    "name": "get_event_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesProperty dimension whose values should be returned
endAtYesEnd timestamp in milliseconds
searchNoSearch returned values
filtersNoAdditional current Umami filter fields
startAtYesStart timestamp in milliseconds
websiteIdYesWebsite UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.1
    • addedInput schema / properties / filters
      Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  "description": "Additional current Umami filter fields",
+  "type": "object"
+}
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Search returned values",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Property dimension whose values should be returned",
+  "enum": [
+    "path",
+    "referrer",
+    "title",
+    "query",
+    "os",
+    "browser",
+    "device",
+    "country",
+    "region",
+    "city",
+    "tag",
+    "hostname",
+    "distinctId",
+    "language",
+    "event",
+    "utmSource",
+    "utmMedium",
+    "utmCampaign",
+    "utmContent",
+    "utmTerm"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "websiteId",
-  "startAt",
-  "endAt"
-]New value: +[
+  "websiteId",
+  "startAt",
+  "endAt",
+  "type"
+]
  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?

With no annotations, the description carries the full burden. "Get" implies a read, but it does not disclose whether results are paginated, capped, sorted, or permission-gated, nor does it explain how the nested filters object affects results. For a 6-parameter analytics query tool, this is a significant gap.

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 or redundancy. It is efficient, though arguably too terse given the tool's parameter complexity.

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?

No output schema and no annotations mean the description must explain behavior, but it does not describe return shape, ordering, limits, or the nested filters semantics. For a required-4-parameter analytics tool with a nested object parameter, this leaves core call-time questions unanswered.

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 coverage is 100%, so every parameter and the type enum are documented in the schema itself; baseline 3 applies. The description adds only the loose framing that returned values are event or session properties, and does not clarify how search, filters, or the type enum interact.

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?

The description states a specific verb ("Get") and resource ("event or session property values") scoped to a website, so an agent understands the basic operation. It does not differentiate itself from closely-named siblings such as get_event_data_values, get_session_data_values, or get_event_data_properties, leaving overlap unresolved.

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?

No guidance on when to use this tool versus get_event_data_values, get_session_data_values, or get_metrics. There is no mention of prerequisites, exclusions, or decision criteria, so the agent must infer selection from the name alone.

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