Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List website session replays

analytics_getWebsiteReplays
Read-onlyIdempotent

Returns a paginated list of recorded sessions for the website, applying date, replay, and search filters. Dates: leave them out for the app's Last 7 days (today and the 6 days before it, from midnight in the site's time zone), or pass range (the app's presets), or startDate and endDate as days (YYYY-MM-DD, both included). timezone defaults to the site's. It calls one fixed endpoint of the Sextant Analytics API (https://sextantweb.com/docs/ai): path filters page URLs, query filters page query strings.

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>"
    },
    "name": "analytics_getWebsiteReplays"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNoOperating system used by the visitor.
tagNoTag attached to the tracked activity.
cityNoCity of the visitor.
pageNoPage number, starting at 1.
pathNoFilter by page URL path.
unitNoTime interval used to group results: minute, hour, day, month, or year.
endAtNoEnd of the date range as a Unix timestamp in milliseconds.
eventNoFilter by custom event name.
matchNoWhether records must match all filters or any filter.
queryNoFilter by page URL query string.
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.
titleNoFilter by page title.
cohortNoID of a saved cohort used to filter visitors.
deviceNoDevice category used by the visitor.
regionNoRegion or subdivision of the visitor.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
browserNoBrowser used by the visitor.
compareNoComparison period: prev for the previous period or yoy for the same period last year.
countryNoCountry code of the visitor.
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.
segmentNoID of a saved segment used to filter results.
startAtNoStart of the date range as a Unix timestamp in milliseconds.
utmTermNoUTM campaign search term.
hostnameNoHostname on which the activity occurred.
languageNoPreferred language reported by the visitor browser.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
pageSizeNoNumber of results per page.
referrerNoFilter by referring URL.
timezoneNoIANA time zone used to interpret dates and group results, for example America/New_York.
eventTypeNoEvent type: 1 for a pageview or 2 for a custom event.
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.
utmMediumNoUTM campaign medium.
utmSourceNoUTM campaign source.
distinctIdNoCustom identifier assigned to the visitor.
maxResultsNoMaximum number of results to include.
utmContentNoUTM campaign content.
minDurationNoMinimum replay duration in seconds.
utmCampaignNoUTM campaign name.
excludeBounceNoSet a non-empty value to exclude visits with only one pageview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior beyond that: pagination, the implicit Last 7 days default window, site-timezone defaulting, and that it hits one fixed endpoint. Return shape and page traversal limits are not described, so it remains partial.

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?

Front-loaded with the operation, then date semantics, then endpoint. Dense but each sentence carries information; only the endpoint URL sentence is marginal for calling the tool correctly.

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?

For a 40-parameter tool with no output schema, the description covers the highest-risk area (date interpretation and defaults) well, but omits return-value expectations, pagination limits, and differentiation from the near-identical replays sibling, which is the most likely source of a mis-selection.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds real semantics beyond the schema: the default date window when date fields are omitted, the mutual exclusivity of range versus startDate/endDate, the inclusive day semantics, and the path-versus-query distinction. It still leaves the 30-plus visitor and UTM filters entirely to the schema.

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: returns a paginated list of recorded sessions for a website, with date, replay and search filters. That is clear, but the sibling catalog contains analytics_getWebsiteSessionReplays, and the description never distinguishes this tool from it, so an agent cannot tell the two apart from the definition alone.

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 the date guidance: omit dates for the app's Last 7 days, or pass range, or startDate/endDate. However there is no statement of when to prefer this tool over analytics_getWebsiteSessionReplays or the saved-replays sibling, and no exclusions are given.

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