Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get a website segment or cohort

analytics_getWebsiteSegment
Read-onlyIdempotent

Returns a saved segment or cohort and its filter parameters for the website.

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>",
      "segmentId": "<segmentId>"
    },
    "name": "analytics_getWebsiteSegment"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
segmentIdYesID of the saved segment or cohort.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 without the description. The description adds one useful behavioral detail — that the response includes the segment's filter parameters — but says nothing about error behavior for unknown segment IDs or whether archived segments are returned. With annotations carrying the main burden, this is adequate but thin.

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?

A single, front-loaded sentence with no filler or redundancy. It is appropriately sized for a simple read tool, though it could have used a second short clause for the when-to-use case at little cost.

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 three-parameter read-only tool with no output schema, the description covers the essential purpose but does not describe the shape of the returned object (segment fields vs. filter structure), which matters since no output schema exists. It is minimally sufficient to invoke correctly but leaves the agent guessing about the response.

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 all three parameters (siteId, objectId, segmentId) are already documented in the schema, including the non-obvious objectId override for short links/pixels. The description adds no parameter-level meaning beyond the generic phrase "for the website," so the baseline 3 applies.

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+resource combination ("Returns a saved segment or cohort and its filter parameters") that makes clear this is a retrieval of a saved segment definition, not a computed analytics report. It does not explicitly contrast itself with siblings like analytics_getWebsite or analytics_getWebsiteBreakdown, so an agent must infer the distinction from the noun alone.

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 guidance on when to call this tool versus the many sibling retrieval tools, nor any stated prerequisite (e.g., needing a segmentId from a list endpoint). The agent is left to infer usage entirely from the name and the required parameters.

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