Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get a visitor's session activity

analytics_getWebsiteSessionActivity
Read-onlyIdempotent

Returns activity for the specified session and sessions linked by visitor identity, using the requested date range and optional distinct ID. Dates: leave them out to read the whole session.

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

Input Schema

NameRequiredDescriptionDefault
endAtNoEnd of the date range as a Unix timestamp in milliseconds.
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.
siteIdYesThe Sextant site ID.
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.
startAtNoStart of the date range as a Unix timestamp in milliseconds.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
sessionIdYesID of the visitor session.
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.
distinctIdNoCustom identifier assigned to the visitor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds the key behavioral fact annotations cannot: it automatically widens scope beyond the given sessionId to all sessions tied to the same visitor identity, which materially changes results. Beyond that it doesn't discuss result volume or how linked sessions are surfaced, so it stops short of a 5.

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?

Two sentences with no filler, and the scope statement is front-loaded ahead of the date note. The only soft spot is that "activity" is doing a lot of vague work in an otherwise precise sentence.

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 9-parameter tool with no output schema, an agent still doesn't know what the returned "activity" contains, how many linked sessions may come back, or how the objectId override interacts with siteId. The scope and date rules are covered, but the return shape and scope size remain unexplained.

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 earns an extra point by adding cross-field semantics the schema doesn't state: omitting date parameters means the whole session is read, and distinctId is framed as an optional modifier rather than a second required identity input.

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?

It states a verb and resource ("Returns activity for the specified session") and adds the non-obvious scope: sessions linked by visitor identity are included too. "Activity" itself is never specified, so the agent knows the shape of the fetch but not of the payload, keeping this below 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 Guidelines3/5

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

The date guidance ("leave them out to read the whole session") is a real usage rule that tells the agent how to get full-session results. However, it never says when to call this instead of the sibling tools like analytics_getWebsiteSession, analytics_getWebsiteSessionStats, or analytics_getWebsiteSessionReplays, so the choice among them is left implicit.

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