Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get AI visibility run

seo_get_ai_visibility_run
Read-onlyIdempotent

Read AI run progress: completed, failed, and pending answer counts, and the recommended next poll interval. Uses no collection credits and does not submit, poll, or retry provider tasks. The workflow advances independently.

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

Input Schema

NameRequiredDescriptionDefault
runIdYes
siteIdYesThe Sextant site ID.

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: it consumes no collection credits, does not drive or retry provider work, and the underlying workflow progresses on its own — all of which affect how an agent should budget and sequence calls.

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 short sentences, front-loaded with the core purpose and what is returned. The credit and no-polling notes earn their place; the closing 'The workflow advances independently' is slightly terse but not wasted.

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?

With no output schema and only two required parameters, the description carries the burden of describing the return payload, and it does so concretely with counts and a poll interval. What's missing is any indication of overall run status semantics (e.g., how 'pending' differs from an incomplete workflow) and where runId originates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: siteId is described in-schema while runId carries only a UUID pattern with no prose. The description never mentions either parameter, so it adds no meaning about what runId refers to, where it comes from, or how siteId scopes the lookup, leaving a real gap for a status-lookup tool.

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 opens with a specific verb and resource ('Read AI run progress') and enumerates the returned signals: completed, failed, and pending answer counts plus a recommended poll interval. That distinguishes it well from siblings like seo_get_ai_visibility_results or seo_get_ai_visibility_answer, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

It makes the use case clear — check progress and get the recommended next poll interval — and rules out behaviors an agent might otherwise assume (it does not submit, poll, or retry provider tasks, and the workflow advances independently). No alternative tool is named for the case where the agent actually wants results or answers, so routing guidance is implied rather than exhaustive.

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