Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get rank tracker

seo_get_rank_tracker
Read-onlyIdempotent

Read-only access to rank tracker configs and their latest results. With trackerId, returns config + a page of latest snapshots (pinned keywords first), including trackingKeywordId for removals and pins, pinned, and googleSerpUrl, a live Google search for the tracked keyword, language, country, and city. Use offset/limit to read additional keywords. Without it, lists all trackers in the project. Uses no credits. Use seo.create_rank_tracker when no tracker exists; then use seo.add_rank_tracking_keywords, seo.remove_rank_tracking_keywords, seo.pin_rank_tracking_keywords, seo_estimate_rank_tracker_cost, or seo.run_rank_tracker to manage it. lastCheckedAt shows position freshness. A null position means the domain was not found in the results the check returned, which can be fewer than serpDepth, so it does not prove the domain ranks below serpDepth.

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

Input Schema

NameRequiredDescriptionDefault
limitNoKeyword rows per page when trackerId is provided. Defaults to 100. Lower this if the text is truncated.
offsetNoKeyword row offset when trackerId is provided. Defaults to 0.
siteIdYesThe Sextant site ID.
trackerIdNoRank tracker config ID. If omitted, lists all rank trackers in the project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses that it uses no credits, that pinned keywords are returned first, that results include a live `googleSerpUrl`, and that `lastCheckedAt` indicates freshness. The null-position caveat (a null does not prove the domain ranks below `serpDepth` because the check may return fewer results) is exactly the kind of interpretation guidance annotations cannot carry. Slightly short of 5 only because pagination/truncation behavior beyond the `limit` note is 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?

Front-loaded with the core read semantics, then paging, then routing, then the interpretation caveat — a sensible order. It is a dense single block covering several distinct concerns, so scannability suffers somewhat, but nearly every clause carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read tool with no output schema, the description supplies the return shape, ordering, cost, freshness field, and a subtle null-semantics warning, plus handoffs to adjacent tools. Nothing material is left for the agent to guess.

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 adds real meaning: it explains what omitting `trackerId` does, what the paginated payload contains per keyword (trackingKeywordId, pinned, googleSerpUrl), and how offset/limit extend the read. That exceeds restating the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (read-only access to rank tracker configs and results) and cleanly splits the two modes: with `trackerId` returns config plus a page of snapshots, without it lists all trackers in the project. This distinguishes it from siblings like seo_estimate_rank_tracker_cost or seo_run_rank_tracker without needing their schemas.

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 routes the agent: use seo.create_rank_tracker when no tracker exists, then hands off to add/remove/pin/estimate/run tools for management. It also gives an in-tool condition (use offset/limit to read additional keywords) so the agent knows how to continue paging rather than switching tools.

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