Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get a visitor session

analytics_getWebsiteSession
Read-onlyIdempotent

Returns details for a website session, including linked visitor identities and whether session deletion is available to the caller.

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

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.
sessionIdYesID of the visitor session.

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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful output context by mentioning linked visitor identities and whether session deletion is available to the caller. It does not cover authorization requirements, pagination, or response shape in more detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler. It communicates the core return behavior immediately and avoids repeating the title or schema details.

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?

For a simple read-only session lookup with full schema coverage and clear annotations, the description provides enough context to invoke the tool correctly. Since there is no output schema, mentioning linked identities and deletion availability is helpful, though it does not fully describe the returned structure.

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 input schema already explains siteId, objectId, and sessionId. The description does not add syntax, constraints, or interpretation beyond the schema. The baseline of 3 is appropriate because the structured parameter documentation is already complete.

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: it returns details for a website session. It also names key returned information, so the agent knows this is the general session-detail tool rather than a session activity, replay, property, or stats tool. It does not explicitly differentiate itself from nearby siblings, which keeps it from 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit when-to-use guidance, prerequisites, or exclusions. It implies usage for retrieving a known session, but with many sibling session tools available, it does not tell the agent when this tool is preferable to session activity, properties, replays, or stats.

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