Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List website filter values

analytics_getWebsiteValues
Read-onlyIdempotent

Returns available values for a website filter, including saved segments or cohorts when requested, to populate filter choices. 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>",
      "type": "<type>"
    },
    "name": "analytics_getWebsiteValues"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
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.
searchNoSearch text used to filter results.
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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior that annotations cannot convey: omitting all dates silently falls back to the app's Last 7 days (today plus the 6 prior days, midnight in the site's time zone) and timezone defaults to the site's zone. It does not disclose anything about the size/shape of the returned value list or any cap on results.

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?

Purpose is front-loaded in the first clause and the date rules follow in a single dense sentence. The date sentence is overloaded with nested parentheticals and would read better as a short list, but no sentence is filler.

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?

With 12 parameters, no output schema, and a required 'type' parameter whose allowed values are never enumerated, the description leaves the agent guessing about what it will actually receive. The date-handling story is thorough, but for a value-listing tool the most important missing piece — what the returned values look like and how 'type' maps to them — is absent.

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 documents range presets, startDate/endDate inclusivity, unit, compare and objectId; the baseline is 3. The description adds real value on one point the schema does not state — the default window when all date fields are omitted — but repeats the preset/inclusive-day semantics already in the schema and says nothing about the required 'type' or 'search' parameters.

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 concrete verb and resource ('Returns available values for a website filter') and adds the purpose ('to populate filter choices'), so the agent knows this is a lookup/enumeration tool rather than a metrics query. However it never distinguishes itself from near-identical siblings such as analytics_getEventDataValues or analytics_getSessionDataValues, and it does not say which values the required 'type' parameter can enumerate, which is the crux of the tool's identity.

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 only implied by the phrase 'to populate filter choices' — the agent must infer that this is the discovery step before calling a metrics/breakdown tool. There is no explicit when-to-use vs. when-not, no named alternative for retrieving actual analytics data, and no stated prerequisites beyond the date-handling hints.

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