Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Export website analytics

analytics_exportWebsite
Read-onlyIdempotent

Returns a base64-encoded ZIP archive containing CSV exports of events, pages, referrers, browsers, operating systems, devices, and countries. Dates: leave them out for the app's Last 7 days (today and the 6 days before it, from midnight in the site's time zone), or pass range (the app's presets), or startDate and endDate as days (YYYY-MM-DD, both included). timezone defaults to the site's.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
unitNoTime interval used to group results: minute, hour, day, month, or year.
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.
compareNoComparison period: prev for the previous period or yoy for the same period last year.
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.
pageSizeNoNumber of results per page.
timezoneNoIANA time zone used to interpret dates and group results, for example America/New_York.
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.
maxResultsNoMaximum number of results to include.

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 readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely new context: the payload is a base64-encoded ZIP of multiple CSVs, and omitted date fields silently fall back to a 7-day window in the site's time zone. It omits any mention of size limits or cost for large exports.

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, front-loaded with what the tool returns, then the date-input decision rules. The second sentence is long and comma-heavy but every clause carries a distinct rule about date resolution rather than filler.

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?

With 13 parameters, no output schema, and a non-obvious binary/ZIP return, the description does the necessary work of explaining the return payload and the date-resolution precedence. Gaps remain around pagination interaction (page/pageSize/maxResults) and what objectId changes about the result, but the core is covered.

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 schema already carries the parameter documentation, including the detailed range preset semantics. The description adds the one thing the schema does not state: the default window when all date fields are omitted, plus the timezone default. The remaining date explanation largely restates the schema.

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 and resource ('Returns a base64-encoded ZIP archive') and enumerates the export contents (events, pages, referrers, browsers, OS, devices, countries), which distinguishes it as a bulk export rather than a single-metric query. It stops short of naming a sibling like analytics_getWebsiteBreakdown as the non-export alternative.

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?

There is useful conditional guidance about date inputs ('leave them out... or pass range... or startDate and endDate'), which tells an agent how to call it. However, there is no explicit statement of when to choose this export over the many analytics_getWebsite* siblings that return the same data as JSON.

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