Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Check whether a replay is saved

analytics_getWebsiteReplaySaved
Read-onlyIdempotent

Returns whether the specified replay is in the website's saved replays.

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_getWebsiteReplaySaved"
  }
}

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.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 fully covered by structured data. The description adds nothing beyond that — no mention of what happens when the replay or site does not exist, or how the boolean is expressed — but it does not contradict anything.

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 short sentence with no wasted words, and the return semantics are front-loaded ('Returns whether...'). It is efficient but offers no further structure because there is nothing else in it.

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?

This is a simple boolean predicate with three fully documented parameters and strong read-only annotations, and the sentence effectively states what comes back. The only minor gap is the absence of any note on behavior for unknown site or replay IDs.

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%, including the optional objectId that redirects the read to a short link or tracking pixel, so the schema already carries parameter meaning. The description mentions only the website scope and does not explain siteId, replayId, or objectId, so it adds no value over the schema; 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 gives a specific verb+resource: it returns a boolean membership answer about a replay in the site's saved replays. That distinguishes it reasonably from list-style siblings like analytics_getWebsiteSavedReplays, but it never explicitly names those alternatives.

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 when-to-use or when-not-to-use guidance and no reference to any alternative such as fetching the replay itself or listing saved replays. The predicate nature of the tool makes its use fairly self-evident, but the definition supplies no routing help.

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