Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get a session replay recording

analytics_getWebsiteReplay
Read-onlyIdempotent

Returns the merged recording events, session details, and event and chunk counts for a replay, with optional stopping points by timestamp, chunk, or event index.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
replayIdYesID of the session replay.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful return-content context (merged events, session details, counts), but says nothing about auth requirements, payload size, or how the merging behaves.

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?

A single well-formed sentence that front-loads the return payload before the optional modifiers. No wasted words, though the trailing stopping-point clause is the source of the schema mismatch.

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 no output schema, the description carries the return-value burden and does describe the payload at a high level. It is incomplete for a replay-retrieval tool: the stopping-point options are unexplained and absent from the schema, and no guidance is given on payload size or selection versus siblings.

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?

Schema coverage is 100%, so the schema already documents siteId, objectId, and replayId. However, the description advertises 'stopping points by timestamp, chunk, or event index' that do not exist in the input schema, which misleads the agent about available parameters rather than clarifying them.

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 uses a specific verb ('Returns') and enumerates the payload: merged recording events, session details, and event/chunk counts for a replay. This clearly distinguishes it from aggregate siblings like analytics_getWebsiteSessionReplays, though it never explicitly contrasts with analytics_getWebsiteReplaySaved.

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 when-to-use or when-not-to-use guidance is given. The mention of 'optional stopping points' hints at partial retrieval but doesn't say when an agent should request a replay versus a saved replay or a session listing, leaving selection to inference.

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