Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List a visitor's session replays

analytics_getWebsiteSessionReplays
Read-onlyIdempotent

Returns a paginated, searchable list of recordings for the specified website session. Dates: leave them out to read the whole session.

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": {
      "siteId": "<siteId>",
      "sessionId": "<sessionId>"
    },
    "name": "analytics_getWebsiteSessionReplays"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
unitNoTime interval used to group results: minute, hour, day, month, or year.
endAtNoEnd of the date range as a Unix timestamp in milliseconds.
rangeNoA preset from the app's date picker, in the site's time zone. 7d, 30d, 90d: today and the days before it, from local midnight. 24h: the current hour and the 23 before it. 12m, 24m, 36m: this month and the months before it, from the 1st. month: this month. today: since local midnight. It gives the same numbers as the app. Leave out the other date fields when you use it.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
compareNoComparison period: prev for the previous period or yoy for the same period last year.
endDateNoLast day of the range (YYYY-MM-DD), included to its end in the site's time zone. An ISO date-time is used as is.
startAtNoStart of the date range as a Unix timestamp in milliseconds.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
pageSizeNoNumber of results per page.
timezoneNoIANA time zone used to interpret dates and group results, for example America/New_York.
sessionIdYesID of the visitor session.
startDateNoFirst day of the range (YYYY-MM-DD), from local midnight in the site's time zone. An ISO date-time is used as is.
maxResultsNoMaximum number of results to include.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior in 'paginated, searchable', but says nothing about default page size, how maxResults interacts with pageSize, or what happens with zero results.

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?

Two short sentences, front-loaded with the verb and scope, with no filler. It is efficient, though extremely terse for a 15-parameter tool.

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?

With 15 parameters, complex date/compare/grouping options, and no output schema, the description should at least sketch what a recording entry contains or how paging behaves. It covers scope and the date-omission behavior but leaves the return shape and most parameter interactions unaddressed.

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 the baseline is 3. The description does add one piece of meaning the schema does not carry — that omitting all date fields reads the entire session — but says nothing about the other 13 parameters, including the potentially confusing mix of range/startDate/endDate/startAt/endAt and compare.

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 ('Returns a paginated, searchable list of recordings') scoped to 'the specified website session', which is enough to separate it from site-wide siblings like analytics_getWebsiteReplays. It does not explicitly name an alternative sibling, so it stops short of a 5.

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?

The only usage guidance is the date hint ('leave them out to read the whole session'), which tells the agent how to get full-session coverage but not when to prefer this tool over analytics_getWebsiteSession or analytics_getWebsiteReplays. Usage is implied by the name and scope rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources