Skip to main content
Glama

Visibility Genies

Estimate rank tracking cost

estimate_rank_tracker_cost
Read-only

Estimate what a tracker costs without buying anything or starting a check. The live figure covers one explicit run_rank_tracker check. For a scheduled tracker the reply also gives the most each queued check, and a month of them, can cost. Pass additionalKeywordCount before adding keywords to see the cost after they are added. A scheduled check never costs more than that figure; a live check only replaces a queued one that was never posted, within what that post would have 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": {
      "projectId": "<projectId>",
      "trackerId": "<trackerId>"
    },
    "name": "estimate_rank_tracker_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
trackerIdYesTracker id from get_rank_tracker.
additionalKeywordCountNoHow many keywords you plan to add. Projects the cost of a scheduled tracker after they are added.

Output Schema

NameRequiredDescriptionDefault
metaNo
methodYes
costUsdYesSecondary: the price before your account's rate. Quote chargedUsd to the person, not this.
trackerIdYes
chargedUsdYesWhat this account is charged for the live check, rounded up to the cent. Quote this to the person.
costCreditsYesSecondary: before your account's rate; used only for the approval limit.
totalChecksYes
devicesCountYes
keywordCountYes
scheduledEstimateNo
existingKeywordCountYes
additionalKeywordCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false and openWorldHint=false, so the description's added burden is behavioral, and it delivers: it explains the live figure covers one explicit run_rank_tracker check, that scheduled trackers also return a per-check and monthly maximum, and that a scheduled check never exceeds that figure. The final sentence about a live check replacing an unposted queued one is dense and somewhat ambiguous, which keeps it off 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.

Conciseness4/5

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

Front-loaded with the purpose and the no-side-effect guarantee, and each sentence carries distinct information. The closing sentence is noticeably tangled ('within what that post would have cost') and would benefit from being split, but no sentence is filler.

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?

With an output schema present and annotations covering the safety profile, the description only needs to explain the cost semantics and return-value meaning, and it does: live vs scheduled figures, the monthly ceiling, and how the projection behaves. Nothing an agent needs to call this correctly is missing.

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%, so all three parameters are already documented in the schema. The description does add purpose-level meaning for additionalKeywordCount (project cost after keywords are added, tied to the 'before adding' workflow), but roughly restates what the schema already says, so 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 and resource ('Estimate what a tracker costs') and immediately scopes it against the real action ('without buying anything or starting a check'), which distinguishes it from run_rank_tracker without needing to name it. An agent can tell this is a dry-run pricing call rather than a mutation.

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 a concrete usage trigger: pass additionalKeywordCount before adding keywords to see post-addition cost. That is clear contextual guidance, but it never states the exclusions explicitly (e.g. 'use run_rank_tracker to actually execute the check') and doesn't mention prerequisites like the tracker needing to exist.

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