Skip to main content
Glama
matious89pl

umami-analytics-mcp

by matious89pl

List sessions

list_sessions
Read-only

Retrieve paginated visitor sessions with browser, OS, device, and geo details. Filter by date range, search, or criteria like URL, referrer, or country.

Instructions

Paginated list of individual visitor sessions over a date range (id, browser, os, device, geo, screen, visits, views, firstAt/lastAt). Supports search + filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNo
tagNo
urlNo
cityNo
hostNo
pageNo1-based page number.
endAtNoExplicit end — ISO 8601, YYYY-MM-DD, or epoch milliseconds. Defaults to now.
eventNo
queryNo
rangeNoRelative window: "24h", "7d", "30d", "12w", "today", "yesterday", "this-week", "last-month", "this-year". Ignored when startAt/endAt are set. Default "7d".
titleNo
deviceNo
regionNo
searchNoSubstring filter.
browserNo
countryNo
startAtNoExplicit start — ISO 8601, YYYY-MM-DD, or epoch milliseconds. Overrides range.
languageNo
pageSizeNoResults per page (max 200).
referrerNo
websiteIdYesUmami website UUID (obtain from list_websites).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
countYes
websiteIdYes
Behavior4/5

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

Annotations declare readOnlyHint, description adds pagination and filter context. No contradictions.

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?

Single concise sentence covering key aspects: pagination, date range, fields, search/filters. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, description gives overview of returned fields. Lacks parameter usage details but adequate overall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Low schema coverage (33%) and description does not detail individual parameters beyond mentioning search/filters. Schema descriptions partially compensate for some fields.

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?

Clearly states it lists paginated sessions with fields listed. Distinguishes from singular get_session by name but not explicit in description.

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 vs alternatives like get_session. Implicit from naming but not stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matious89pl/umami-analytics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server