Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List website segments and cohorts

analytics_getWebsiteSegments
Read-onlyIdempotent

The site's saved segments (filters) or cohorts (visitors who did something in a period).

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

Input Schema

NameRequiredDescriptionDefault
typeYesType of resource or analytics dimension to return.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 the safety profile is fully covered by structured data. The description adds useful domain semantics (segments are filters; cohorts are visitors who did something in a period) but says nothing about result volume, pagination, or what an empty site returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with parenthetical definitions, front-loaded on the resource being returned. Every clause carries information; there is no boilerplate.

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?

For a simple read-only list tool with full schema descriptions and complete annotations, the definition covers enough to invoke it correctly. It is thin on what the response looks like (no output schema exists, so return shape is undescribed) and on the objectId override, which an agent could easily misapply.

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, but the description earns an extra point by defining the two enum values that the schema describes only vaguely as 'type of resource or analytics dimension'. It does not explain the non-obvious 'objectId' override (reading analytics for a short link/pixel instead of the site), leaving that to 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 names the two resources returned (saved segments/filters and cohorts of visitors who did something in a period), which is clearer than the title alone. It lacks a verb (the 'list' action comes only from the title) and gives no contrast with the many sibling analytics_getWebsite* endpoints, so it is clear but undifferentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no guidance on picking 'segment' vs 'cohort' for a given analytical question, and no mention of alternatives among the sibling tools. The only implicit signal is that the tool returns whichever of the two resource kinds the required 'type' selects.

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