Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Estimate rank tracker cost

seo_estimate_rank_tracker_cost
Read-onlyIdempotent

Estimate rank tracker cost without spending credits or starting a check. Each estimate is the most a check can cost: it includes up to two queued retries of every keyword/device check, which run only for checks that error or read as lost, so most checks cost less. The live estimate covers one explicit seo.run_rank_tracker check. For a scheduled tracker, the response also includes the queued per-check and approximate monthly recurring cost. Pass additionalKeywords before adding keywords to project the post-add cost.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.
trackerIdYesRank tracker ID from seo.get_rank_tracker.
additionalKeywordsNoKeywords you plan to add. Include these before adding to a scheduled tracker so the response projects its recurring per-check and monthly cost; keywords with search operators such as site: cost 5x. Overrides additionalKeywordCount.
additionalKeywordCountNoNumber of keywords you plan to add, priced as plain keywords. Prefer additionalKeywords when you know them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say read-only/idempotent/non-destructive; the description adds the substantive behavior an agent needs: no credits consumed, estimate is an upper bound that includes up to two queued retries per keyword/device, retries only fire for errored or lost checks so typical cost is lower, and scheduled trackers additionally return queued per-check and monthly recurring figures. That is genuine context beyond the structured fields.

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?

The lead sentence front-loads the key value proposition (no credits, no check started), and the following sentences each carry real information about how the estimate is computed. It is dense but not padded, though the retry explanation could be tightened slightly.

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 does explain what the response contains for both the live and scheduled cases (live estimate for one explicit check; queued per-check and approximate monthly cost for scheduled trackers). An agent can call and interpret it correctly; only finer response-shape details are absent.

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 coverage is 100%, and the schema itself already documents siteId, trackerId, the 5x cost of search-operator keywords, the 1000 max, and that additionalKeywords overrides additionalKeywordCount. The description's note to pass additionalKeywords before adding keywords largely restates the schema text, so it adds little new meaning; baseline 3 applies.

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 (Estimate) and resource (rank tracker cost) plus a differentiating qualifier: no credits spent and no check started. It is clearly distinguishable from the sibling seo_estimate_ai_visibility_cost and from seo_get_rank_tracker, which fetches the tracker rather than pricing it.

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?

Gives concrete usage context: call it before running an explicit seo.run_rank_tracker check, and pass additionalKeywords before actually adding keywords so the response projects post-add cost. It does not name an alternative tool to use instead when the user wants real results rather than an estimate, so it stops short of explicit when-not 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