Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get ranked website metrics

analytics_getWebsiteMetrics
Read-onlyIdempotent

Returns the most frequent values for a dimension such as pages, referrers, countries, browsers, campaigns, or events. Counts pageviews or events for activity dimensions and unique visitors for visitor dimensions. 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. It calls one fixed endpoint of the Sextant Analytics API (https://sextantweb.com/docs/ai): path filters page URLs, query filters page query strings.

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>",
      "type": "<type>"
    },
    "name": "analytics_getWebsiteMetrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNoOperating system used by the visitor.
tagNoTag attached to the tracked activity.
cityNoCity of the visitor.
pathNoFilter by page URL path.
typeYesDimension to rank: path, entry, exit, title, query, hostname, referrer, domain, channel, event, tag, browser, os, device, screen, language, country, region, city, distinctId, utmSource, utmMedium, utmCampaign, utmContent, utmTerm.
unitNoTime interval used to group results: minute, hour, day, month, or year.
endAtNoEnd of the date range as a Unix timestamp in milliseconds.
eventNoFilter by custom event name.
limitNoMaximum number of rows to return.
matchNoWhether records must match all filters or any filter.
queryNoFilter by page URL query string.
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.
titleNoFilter by page title.
cohortNoID of a saved cohort used to filter visitors.
deviceNoDevice category used by the visitor.
offsetNoNumber of rows to skip before returning results.
regionNoRegion or subdivision of the visitor.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
browserNoBrowser used by the visitor.
compareNoComparison period: prev for the previous period or yoy for the same period last year.
countryNoCountry code of the visitor.
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.
segmentNoID of a saved segment used to filter results.
startAtNoStart of the date range as a Unix timestamp in milliseconds.
utmTermNoUTM campaign search term.
hostnameNoHostname on which the activity occurred.
languageNoPreferred language reported by the visitor browser.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
referrerNoFilter by referring URL.
timezoneNoIANA time zone used to interpret dates and group results, for example America/New_York.
eventTypeNoEvent type: 1 for a pageview or 2 for a custom event.
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.
utmMediumNoUTM campaign medium.
utmSourceNoUTM campaign source.
distinctIdNoCustom identifier assigned to the visitor.
utmContentNoUTM campaign content.
utmCampaignNoUTM campaign name.
excludeBounceNoSet a non-empty value to exclude visits with only one pageview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real substance beyond that: counting semantics differ by dimension type (pageviews/events for activity dimensions, unique visitors for visitor dimensions), the default Last-7-days window is defined precisely down to local midnight and the site's time zone, and it notes path filters URLs while query filters query strings. Pagination behavior and the row shape are still unstated.

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?

The purpose sentence comes first and the operational detail follows; almost every sentence carries information an agent needs before calling. The trailing sentence about the fixed Sextant endpoint is somewhat incidental, though the path/query filter clarification inside it is useful.

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 39-parameter tool with no output schema and only safety-oriented annotations, the description covers the hard parts: what the ranked rows represent, how counts are computed per dimension type, and how dates and time zones resolve. The main residual gap is return shape and paging (how limit/offset affect output, whether compare adds extra fields), which an agent must infer.

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 above that by adding semantics the schema cannot express. It explains the mutual exclusivity and time-zone behavior of range versus startDate/endDate/startAt/endAt, states that timezone defaults to the site's, and clarifies the distinction between the path and query filter parameters, which their terse schema descriptions do not make obvious.

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 uses a specific verb and resource: 'Returns the most frequent values for a dimension' and enumerates example dimensions (pages, referrers, countries, browsers, campaigns, events). That is clearly more informative than the title alone. It does not, however, distinguish this tool from near-siblings such as analytics_getWebsiteBreakdown or analytics_getWebsiteExpandedMetrics, which plausibly return similar ranked rows.

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?

Usage is implied by the dimension-ranking framing and the date-selection rules (omit dates for Last 7 days, or pass range, or startDate/endDate), which is genuinely helpful operational guidance. There is no explicit statement of when to prefer this tool over the other breakdown/metric siblings, and no exclusion such as 'do not use for time series' (that appears to be analytics_getWebsiteEventSeries or analytics_getWebsitePageviews).

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