Skip to main content
Glama
Sign In
umami-mcp

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_sessions_weekly

Retrieve weekly session data for a website using Umami Analytics, specifying date range, timezone, and optional filters to analyze visitor traffic trends.

Instructions

Get weekly session data 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>",
      "timezone": "<timezone>"
    },
    "name": "get_sessions_weekly"
  }
}

Input Schema

NameRequiredDescriptionDefault
endAtYesEnd timestamp in milliseconds
filtersNoAdditional Umami v3 filters such as country, device, browser, tag, UTM fields, segment, or cohort
startAtYesStart timestamp in milliseconds
timezoneYesIANA timezone (e.g. 'Asia/Seoul')
websiteIdYesWebsite UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.1
    • addedInput schema / properties / filters
      Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  "description": "Additional Umami v3 filters such as country, device, browser, tag, UTM fields, segment, or cohort",
+  "type": "object"
+}
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA timezone (e.g. 'Asia/Seoul')",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "websiteId",
-  "startAt",
-  "endAt"
-]New value: +[
+  "websiteId",
+  "startAt",
+  "endAt",
+  "timezone"
+]
  2. First observedv1.2.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden and discloses almost nothing. It does not clarify what a 'week' boundary means, how the required timezone affects bucketing, what the response shape is, or any rate/aggregation limits.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, which is structurally clean. But the brevity comes at the cost of under-specification rather than efficiency, so it does not earn a high score.

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?

With 5 parameters, 4 required, a nested filters object, no output schema, and no annotations, the description should explain the weekly aggregation semantics and return shape. It provides none of that, leaving the agent unable to predict the result of a call.

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% (websiteId, startAt, endAt, timezone, filters all documented in-schema), so the schema does the heavy lifting and baseline 3 applies. The description adds no extra meaning, such as whether startAt/endAt are snapped to week boundaries before aggregation.

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 weekly session data') scoped to a website, which is clearer than a generic 'get sessions'. However, it never differentiates itself from adjacent siblings like get_sessions, get_session_stats, or get_session_activity, so an agent must guess which one returns weekly aggregates.

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 guidance on when to use this versus get_sessions or get_session_stats, no mention of prerequisites, and no exclusions. The only usage signal is the word 'weekly' in the name, which is not explained.

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