Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get AI visibility results

seo_get_ai_visibility_results
Read-onlyIdempotent

For a normal review make one run-wide call with these top-level arguments (there is no filters object): runId null (or a manual run's runId), topic null, engines null, promptId null, cursor null, competitorGap false; never enumerate every engine or prompt. Use engines to request one or more engines in a single filtered call. Then read sources once for its returned runId and inspect 2-3 answer examples. Derive competitor gaps from returned rows or make a separate gap query; never carry competitorGap=true into overall source or branded-diagnostic reads. Read paginated prompt/engine observations and brand comparison counts over answered collections. Defaults to neutral prompts in the latest baseline/scheduled run, excluding manual checks unless the project has only manual checks; request branded=all to include branded diagnostics. Reuse the returned runId and filters for source analysis. No full answers or collection; use observation IDs with seo_get_ai_visibility_answer. Supports prompt history and competitor gaps.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
runIdNoOmit or null for the latest baseline/scheduled run, or the latest manual check when there is none. Reuse the returned runId for related source/answer reads. Do not use the string all.
topicNoOmit or null for all topics in the run. Filter by an exact saved topic name only when requested; do not use the string all.
cursorNoOmit or null for the first page. Use only a returned nextCursor for another page; do not use the string all.
siteIdYesThe Sextant site ID.
brandedNoneutral
enginesNoOmit or null for all engines in one call. Provide one or more engines for an explicitly requested subset, or an empty array for no engines. Do not make separate calls for each engine or use the string all.
promptIdNoOmit or null for all prompts in the run. Provide an exact prompt ID only when requested; includeHistory returns that prompt's prior observations. Do not use the string all.
competitorGapNoUse false for the initial review, overall sources and branded diagnostics. True restricts rows to answers where a competitor appears and your brand is absent; an empty gap subset does not mean answer details are missing.
includeHistoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds real behavioral context: the default run selection is the latest baseline/scheduled run and manual checks are excluded unless no baseline exists, results are paginated, and full answers are deliberately omitted. Some of this detail duplicates schema-level hints rather than adding new information, keeping it below a 5.

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

Conciseness2/5

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

A single dense wall of run-on sentences with the purpose statement placed mid-paragraph, so the definition is not front-loaded. Nearly all content is substantive, but the lack of separation between default-behavior, filtering, pagination and handoff rules makes it hard to scan and increases the risk of an agent missing a constraint.

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 10-parameter read tool with no output schema and no nested objects, the description covers defaults, filtering semantics, pagination convention, what is intentionally not returned, and where to get answer detail. Remaining gaps are minor, such as the shape of comparison counts and limit behavior.

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?

With 70% schema description coverage, the schema already documents runId, topic, cursor, engines, promptId and competitorGap semantics in near-identical language, so much of the description's parameter prose restates structured data. The added value is mainly the cross-parameter rule (don't set competitorGap=true for overall/branded reads, set branded=all to include branded diagnostics), which is genuine but narrow.

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 core purpose is stated concretely: "Read paginated prompt/engine observations and brand comparison counts over answered collections," with an explicit exclusion of full answers routed to seo_get_ai_visibility_answer. However, the statement of what the tool does is buried in the middle of a long prescriptive paragraph rather than up front, so the agent must read several sentences before learning the resource.

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

Usage Guidelines5/5

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

Explicitly prescribes the call pattern ("make one run-wide call" with listed top-level arguments, "never enumerate every engine or prompt"), names when to use `engines` instead, and warns against carrying competitorGap=true into source or branded-diagnostic reads. It also names the sibling handoff for answer bodies and the reuse rule for returned runId and filters, leaving little to inference.

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