Skip to main content
Glama

Visibility Genies

Read rank history

get_rank_history
Read-only

What moved in a rank tracker between two days: for each keyword and device, its position on the first day and on the last (its newest check by the end of each day), and the change, positive when it moved up, as the Rank Tracking page counts it. Sorted by the size of the move. Give trackingKeywordId to add every check of one keyword between the two days. Positions reach back only as far as the plan keeps history. Free: it reads saved checks and buys nothing; run_rank_tracker buys new ones.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
deviceNo
offsetNo
endDateNoLast day, YYYY-MM-DD in UTC. Defaults to today.
movedOnlyNoOnly keywords whose position changed between the two days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoFirst day, YYYY-MM-DD in UTC. Defaults to 30 days before endDate.
trackerIdYesRank tracker id, from get_rank_tracker.
trackingKeywordIdNoOne keyword's id from these rows: adds every check of it between the two days.

Output Schema

NameRequiredDescriptionDefault
metaNo
rowsYes
endDateYes
historyNo
startDateYes
totalCountYes
unreadRunsYes

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 already cover the safety profile (readOnly, non-destructive), yet the description still adds real behavioral context: history depth is capped by plan retention, the call consumes no credits, and 'position on a day' means the newest check by the end of that day. The sorting rule and sign convention are also disclosed, which an agent cannot infer from 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?

Front-loaded with what the tool returns, then refinements, then the cost/routing note — every sentence carries information. The prose is dense and slightly run-on in the opening clause, but no sentence is filler.

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?

For a 9-parameter history read with an output schema, the definition covers semantics, ordering, retention limits, and billing implications, which is most of what an agent needs. Gaps are minor: pagination defaults and the movedOnly filter are left entirely to the schema.

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?

With 67% schema description coverage the baseline is 3. The description reinforces the meaning of the date window and trackingKeywordId, and adds that results are broken out per device, but it says nothing about limit, offset, or movedOnly, leaving pagination and filtering behavior to the schema.

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 resource and operation: per-keyword, per-device positions on the first and last day of a window plus the delta. It also specifies the sort order and the sign convention (positive = moved up), which lets an agent distinguish it from get_rank_tracker and run_rank_tracker 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?

Explicitly routes cost-sensitive calls: this tool 'reads saved checks and buys nothing; run_rank_tracker buys new ones' — a clear when-to-use-this-vs-sibling rule. It also states the condition for passing trackingKeywordId (to expand into every check of one keyword). It stops short of stating exclusions such as when to prefer get_serp_history or get_local_rank_grid.

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