Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get AI visibility tracker

seo_get_ai_visibility_tracker
Read-onlyIdempotent

Read AI tracking setup, topics, exact prompts, the project-context brand and competitors that answers are matched against, engine/country capabilities, and recent runs. Returns configured=false when absent. Uses no collection credits; never starts or polls a provider task.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral facts beyond them: the configured=false sentinel for absent setup, zero credit consumption, and the guarantee that no provider task is started or polled. Those are exactly the details an agent needs before deciding whether this call is safe and free.

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 tight clauses with the return contents front-loaded and the behavioral guarantees (free, non-triggering) at the end. The enumeration is dense but every item corresponds to a real payload section, so there is little waste.

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, the description takes on the job of describing returns and does so by enumerating the payload sections plus the configured=false case. Minor gaps remain (how many 'recent runs' are returned, ordering), but an agent can call this correctly from what is written.

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?

The single siteId parameter is fully documented in the schema (100% coverage), so the schema carries the load and baseline 3 applies. The description adds no meaning about siteId or what happens if an unknown site is passed, but nothing is missing either.

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?

Specific verb 'Read' plus an enumerated resource list (tracking setup, topics, prompts, brand/competitor context, engine/country capabilities, recent runs) makes the tool's scope unambiguous. It implicitly separates configuration-reading from the sibling result/run/sources tools, but never names those siblings to sharpen the distinction.

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 implied rather than stated: 'Uses no collection credits; never starts or polls a provider task' tells the agent this is a free, non-triggering read, which contrasts with the estimate/run siblings. However, there is no explicit 'call this first' or 'use seo_get_ai_visibility_results instead when you want answers' routing guidance.

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