Skip to main content
Glama

Visibility Genies

Read rank trackers

get_rank_tracker
Read-only

Read-only view of the project's rank trackers and their latest results. Uses no credits. When no tracker exists yet, call create_rank_tracker, then manage it with add_rank_tracking_keywords, remove_rank_tracking_keywords, estimate_rank_tracker_cost or run_rank_tracker. lastCheckedAt shows how fresh the positions are. With trackerId the result also carries each keyword's trackingKeywordId, which removals need. A position marked unconfirmed is a drop from a single reading that the next check has not yet confirmed.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
trackerIdNoRank tracker config ID. Omit to list every tracker in the project.

Output Schema

NameRequiredDescriptionDefault
metaNo
configNo
configsNo
resultsNo
waitingForNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that: zero credit cost, the meaning of lastCheckedAt as a freshness signal, how trackerId changes the returned payload, and the domain caveat that an 'unconfirmed' position is a single-reading drop not yet verified.

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 purpose and cost profile, then routing, then output semantics in short declarative sentences. It is dense rather than padded, though the lastCheckedAt and unconfirmed explanations partly overlap with what the output schema can show.

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 two-parameter read tool with full schema coverage, annotations and an output schema, nothing an agent needs to call it correctly is missing: cost, freshness interpretation, sibling routing and the payload difference when trackerId is set are all present.

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 both parameters are already documented. The description still adds meaning by stating that supplying trackerId causes each keyword's trackingKeywordId to be returned and that removals depend on it, which the schema does not convey.

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 view of the project's rank trackers and their latest results') and implicitly scopes it against the mutation siblings it names. An agent can distinguish it from run_rank_tracker or create_rank_tracker without opening a schema.

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?

Gives explicit routing: when no tracker exists, call create_rank_tracker; for keyword or cost management, use add_rank_tracking_keywords, remove_rank_tracking_keywords, estimate_rank_tracker_cost or run_rank_tracker. It also notes the call uses no credits, which is a practical when-to-use signal.

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