Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List saved session replays

analytics_getWebsiteSavedReplays
Read-onlyIdempotent

Returns a paginated, searchable list of replays saved for the 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": {
      "siteId": "<siteId>"
    },
    "name": "analytics_getWebsiteSavedReplays"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
pageSizeNoNumber of results per page.
maxResultsNoMaximum number of results to include.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 that results are paginated and searchable, which is genuinely useful behavioral context beyond the annotations, but it says nothing about ordering, result counts, or what a replay record contains.

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 with no filler and the key qualifiers ('paginated', 'searchable', 'saved') front-loaded. It is efficient but thin enough that it leaves no room for the usage routing an agent would need.

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 six parameters at full schema coverage and annotations carrying the safety profile, the description only needs to establish the return shape and routing. It establishes the return shape ('paginated, searchable list of replays') but omits when to prefer it over the three similarly named replay tools, leaving a real gap for a 6-parameter listing tool.

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 page, pageSize, search, siteId, objectId, and maxResults are all documented in the schema itself. The description's 'paginated, searchable' phrasing reinforces the paging and search parameters but adds no semantics beyond them, so baseline 3 applies.

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 names a specific verb ('Returns a ... list') and resource ('replays saved for the website'), and the 'saved' qualifier distinguishes it from the unsaved replay listings among its siblings. It stops short of explicitly contrasting itself with those siblings, so the differentiation must be inferred from the adjective.

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 choose this tool over analytics_getWebsiteSessionReplays, analytics_getWebsiteReplays, or analytics_getWebsiteReplaySaved. The agent must guess from the word 'saved' alone, with no stated preconditions or exclusions.

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