Skip to main content
Glama
Sign In
umami-mcp

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_session_activity

Retrieves pages visited and events fired for a specific Umami website session within a timestamp range to analyze user activity.

Instructions

Get activity log for a specific session (pages visited, events fired)

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>",
      "sessionId": "<sessionId>",
      "startAt": "<startAt>",
      "endAt": "<endAt>"
    },
    "name": "get_session_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
endAtYesEnd timestamp in milliseconds
startAtYesStart timestamp in milliseconds
sessionIdYesSession UUID
websiteIdYesWebsite UUID
distinctIdNoOptional linked distinct ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.1
    • addedInput schema / properties / distinctId
      Added value: +{
+  "description": "Optional linked distinct ID",
+  "type": "string"
+}
    • addedInput schema / properties / endAt
      Added value: +{
+  "description": "End timestamp in milliseconds",
+  "type": "number"
+}
    • addedInput schema / properties / startAt
      Added value: +{
+  "description": "Start timestamp in milliseconds",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "websiteId",
-  "sessionId"
-]New value: +[
+  "websiteId",
+  "sessionId",
+  "startAt",
+  "endAt"
+]
  2. First observedv1.2.1

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. 'Get' implies a read operation and the parenthetical describes the content, but the description does not disclose pagination, limits, permissions, ordering, or empty-result behavior.

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?

The description is a single front-loaded sentence with no wasted words. It states the resource, scope, and content examples efficiently.

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?

The tool has five parameters, four required, no output schema, and no annotations. The description tells the agent what kind of data is returned but not its structure, ordering, pagination, or edge cases, leaving meaningful gaps for an agent invoking it correctly.

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 are documented in the schema. The description does not add meaning beyond the schema, such as how startAt/endAt bound the activity or what distinctId affects, so the baseline of 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?

The description states a specific verb and resource: get the activity log for a specific session, with examples of the content (pages visited, events fired). It is clear what the tool returns, but it does not explicitly differentiate itself from nearby siblings such as get_session or get_session_stats.

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?

Usage is implied by 'for a specific session' and the returned content, but there is no explicit guidance on when to use this instead of get_session, get_sessions, get_session_stats, or session replay tools. The agent must infer the selection criteria.

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