Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get numeric session property statistics

analytics_getSessionDataNumericStats
Read-onlyIdempotent

Returns the total, average, median, minimum, and maximum of the specified numeric session property for the selected date range and filters. 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>",
      "propertyName": "<propertyName>"
    },
    "name": "analytics_getSessionDataNumericStats"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNoOperating system used by the visitor.
tagNoTag attached to the tracked activity.
cityNoCity of the visitor.
pathNoFilter by page URL path.
endAtNoEnd of the date range as a Unix timestamp in milliseconds.
eventNoFilter by custom event name.
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.
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.
propertyNameYesName of the custom event or session property.
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.7/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is additive and it delivers: it discloses that this hits one fixed endpoint of the Sextant Analytics API, that timezone defaults to the site's, and how the default 7-day window is anchored to local midnight. That said, it says nothing about how session-level numeric property values are aggregated across sessions (e.g. per-session vs. per-event rollup), which matters for interpreting the median.

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?

Three sentences, front-loaded with the return shape, then date semantics, then endpoint provenance. Dense without being padded, though the final sentence pads on both API provenance and the path/query distinction, and the date sentence restates much of what the range enum already documents.

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 34-parameter tool with no output schema, it does the essential work of enumerating the five returned statistics and how the date window defaults, which is what an agent needs to call it correctly without inspecting a return schema. The remaining gap is behavioral: no note that propertyName must refer to a numeric property, which is the most likely cause of a failed call.

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 coverage is 100% across 34 parameters, so the baseline is 3 and the schema already explains range presets, startDate/endDate inclusivity, timezone, and match. The description adds only marginal value beyond that: the mutual exclusivity between omitting dates, passing range, and passing startDate/endDate, plus the distinction that path filters URLs while query filters query strings. It does not explain the interplay of propertyName with event filters or segment/cohort selection.

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?

States a specific verb and resource with precise output shape: total, average, median, minimum and maximum of a named numeric session property over a date range with filters. That is unambiguous about what comes back, though it never names the sibling it should be preferred over (e.g. analytics_getEventDataNumericStats or analytics_getSessionDataPropertySeries), so the agent must infer the difference from tool names alone.

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-selection guidance (omit for Last 7 days, or pass range, or startDate/endDate) is really parameter usage, not tool-selection guidance. There is no statement of when to choose this aggregate-stats tool versus the series, pivot, or event-data numeric equivalents, so an agent has to guess from the name. The doc link to the Sextant API is a mild substitute for explicit routing.

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