Skip to main content
Glama
Sign In
umami-mcp

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_session_data_values

Retrieve aggregated session property value counts for an Umami website within a specified time range and optional filters.

Instructions

Get session data values (aggregated counts for session properties) 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_session_data_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
endAtYesEnd timestamp in milliseconds
filtersNoAdditional current Umami filter fields
startAtYesStart timestamp in milliseconds
dataTypeNoOptional Umami data type code
websiteIdYesWebsite UUID
propertyNameNoFilter by property name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
+}
  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. It adds only 'aggregated counts for session properties' and says nothing about whether it is read-only (implied only by 'Get'), what permissions/scoping apply, how results are ordered or limited, or what the response contains despite there being no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with a clarifying parenthetical and zero filler. Nothing in it could be removed without losing information.

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?

This is a six-parameter analytics query tool with a nested filters object, no annotations, and no output schema, yet the description is one sentence. It leaves the agent without a picture of the returned aggregation shape, the meaning of dataType, or how the required time range and propertyName filter scope the results.

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 six parameters including the nested filters object and the optional dataType/propertyName are already documented in the schema. The description adds no syntax, format, or interaction detail (e.g. how propertyName interacts with filters) beyond what the schema provides, so the 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 ('Get session data values') and clarifies with a parenthetical that these are aggregated counts for session properties, which distinguishes it from get_session_data_properties. It stops short of explicitly contrasting with the near-identical get_event_data_values sibling, leaving the agent to infer the session-vs-event distinction.

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?

The description gives no indication of when to use this versus get_session_data_properties, get_session_stats, get_event_data_values, or get_stats. No prerequisites, no exclusions, no alternative routing.

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