Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get website performance metrics

analytics_getWebsitePerformanceMetrics
Read-onlyIdempotent

One Core Web Vital for each page, page title, device or browser, slowest first. 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_getWebsitePerformanceMetrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNoOperating system used by the visitor.
tagNoTag attached to the tracked activity.
cityNoCity of the visitor.
pathNoFilter by page URL path.
typeYesType of resource or analytics dimension to return.
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.
metricNoNumeric aggregation to calculate for the selected property.
regionNoRegion or subdivision of the visitor.
siteIdYesThe Sextant site ID.
browserNoBrowser used by the visitor.
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 read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: results are ordered slowest-first, the implicit default window is the app's Last 7 days from local midnight, timezone defaults to the site's, and the date modes are mutually exclusive. It does not describe result shape or limits, but that is minor against the annotation coverage.

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 output shape and ordering are front-loaded, followed by the date semantics, which are the highest-risk parameters. Sentences are dense but each carries information; the closing API/doc note is the least load-bearing part.

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 37-parameter read-only tool with full schema coverage and no output schema, the description covers what is returned, ordering, the default date window, and date-mode exclusivity. Gaps remain around limit/pagination behavior and how the many visitor filters (country, device, cohort, segment) combine, but nothing critical to calling it correctly is missing.

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 3 would be the baseline, but the description genuinely adds meaning the schema lacks: that omitting all date fields yields the app's Last 7 days, that the three date modes are alternatives, that startDate/endDate are inclusive day boundaries, and that path/query map to page URL path vs query string. It says nothing extra about type, metric, limit, or the filter/match interaction, which keeps it from a 5.

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?

"One Core Web Vital for each page, page title, device or browser, slowest first" names the returned resource, the grouping dimension (mapping to the type enum), and the ordering. It is clearly a performance-metrics tool rather than a generic metrics tool. It does not explicitly name a sibling it is not (e.g. PerformanceChart or PerformanceStats), so it stops short of 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 description gives solid usage rules for the date parameters: omit them for the app's Last 7 days, or use range, or use startDate/endDate. However, it offers no guidance on when to choose this tool over analytics_getWebsitePerformanceStats or analytics_getWebsitePerformanceChart, and no exclusions are stated.

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