Skip to main content
Glama

Visibility Genies

Run a rank check

run_rank_tracker

Starts one live rank check for every keyword and device on a tracker. Estimated price: about $0.20 per 10 keyword and device checks at the default depth with AI Overviews; estimate_rank_tracker_cost gives the tracker's total for free. That total with its margin is checked against the agent spend limit before anything starts; the checks are then charged as they run, never above the amount allowed. A check already running is reported and not charged, and the tracker's schedule is unchanged. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": "run_rank_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
trackerIdYesRank tracker ID from get_rank_tracker.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
runIdNo
startedYes
trackerIdYes
blockingRunIdNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, open-world, non-destructive operation; the description goes well beyond that with the per-10-check price, the pre-flight limit check, hold-while-running versus charged-what-was-bought semantics, and the note that an already-running check is reported and not charged. It also states a side-effect boundary (the tracker's schedule is unchanged) and the exact refusal payload, which the agent needs to recover gracefully.

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?

Purpose is front-loaded and the cost-gating rules follow in a sensible order, with no filler sentences. There is mild repetition around the charging ceiling ('never above the amount allowed', 'never more') that could be tightened without losing meaning.

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 billed, open-world mutation tool this covers the essentials an agent must know before calling: cost, spend-limit gating, hold-and-charge behavior, and the refusal recovery path. With an output schema present, no return-value explanation is needed and nothing operationally important 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 description coverage is 100%, so projectId, trackerId and approvedMaxCostUsd are already documented, including the warning not to set approvedMaxCostUsd without asking. The description adds only the surrounding refusal-then-retry narrative rather than new field-level meaning, so the 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?

The first sentence gives a specific verb and resource with scope: 'Starts one live rank check for every keyword and device on a tracker.' That is enough to separate it from create_rank_tracker, get_rank_tracker and estimate_rank_tracker_cost without opening any schema.

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 points to estimate_rank_tracker_cost as the free way to get the total and spells out the refusal-and-retry path with approvedMaxCostUsd, including the instruction to ask the user first. It does not explicitly contrast running a fresh check against reading past results via get_rank_history, so the alternative routing is clear but not 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