Skip to main content
Glama
Data-Dive-Tools

DataDive MCP

Official
by Data-Dive-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Keyword Rankings for a Rank Radar

get_rank_radar_data
Read-only

Analyze keyword ranking trends over time by retrieving historical data for a specified Rank Radar and date range, including daily organic, sponsored, and impression ranks.

Instructions

Use this to analyze keyword ranking trends over time. Requires startDate and endDate (yyyy-mm-dd), at most 90 days apart. Retrieves historical keyword ranking data for the specified Rank Radar within the date range. Without currentPage and pageSize it returns every active keyword in one result. To read one page instead — faster for large Rank Radars — pass currentPage and/or pageSize (max 100) and continue with currentPage + 1 while hasNext is true. The response carries currentPage, pageSize, total, lastPage, hasNext and hasPrev; total is the Rank Radar's active keyword count. Paused keywords are not included. Each keyword has id, keyword, searchVolume, relevancy, ranks (per-day { date, organicRank, sponsoredRank, impressionRank }), and any highlight annotations. A rank of 101 means the product was not in the top 100 results that day. For PPC metrics use get_rank_radar_ppc_data; for Search Query Performance use get_rank_radar_sqp_data. Use after list_rank_radars to discover a rankRadarId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateYesEnd date of the range, yyyy-mm-dd (e.g. 2024-04-26). Must be on or after startDate, and at most 90 days after it.
pageSizeNoKeywords per page (max 100). Defaults to 20.
startDateYesStart date of the range, yyyy-mm-dd (e.g. 2024-03-26).
currentPageNoPage of keywords, 1-indexed. Defaults to 1.
rankRadarIdYesThe Rank Radar UUID (from `list_rank_radars`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.16.1
    • addedInput schema / properties / currentPage
      Added value: +{
+  "description": "Page of keywords, 1-indexed. Defaults to 1.",
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / endDate / description
      Previous value: -"End date for the ranking data range, yyyy-mm-dd (e.g. 2024-04-26). Must be on or after startDate."New value: +"End date of the range, yyyy-mm-dd (e.g. 2024-04-26). Must be on or after startDate, and at most 90 days after it."
    • addedInput schema / properties / pageSize
      Added value: +{
+  "description": "Keywords per page (max 100). Defaults to 20.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / startDate / description
      Previous value: -"Start date for the ranking data range, yyyy-mm-dd (e.g. 2024-03-26)."New value: +"Start date of the range, yyyy-mm-dd (e.g. 2024-03-26)."
  2. First observedv0.8.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, but the description goes well beyond that: the 90-day date-range cap, that paused keywords are excluded, that rank 101 means outside the top 100, the pagination termination rule (hasNext), and the full response field list. This is rich behavioral context that annotations do not cover.

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 purpose and constraints, and nearly every sentence carries useful information. It is somewhat dense and long, but the content is largely non-redundant rather than padding.

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 no output schema, the description compensates by enumerating response fields (currentPage, pageSize, total, lastPage, hasNext, hasPrev) and the per-keyword shape (ranks, searchVolume, relevancy, highlights), so an agent knows exactly what it gets back.

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 already 100%, yet the description adds real meaning about how currentPage/pageSize interact and the max of 100. However, it claims omitting both returns 'every active keyword in one result,' which sits awkwardly against the schema's stated pageSize default of 20 — a minor inconsistency that costs it a point.

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 ('Retrieves historical keyword ranking data for the specified Rank Radar') and explicitly names the sibling tools for adjacent data (get_rank_radar_ppc_data, get_rank_radar_sqp_data), so an agent can disambiguate without opening schemas.

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 when-to-use context, the prerequisite workflow ('Use after list_rank_radars to discover a rankRadarId'), the alternative tools for PPC and SQP metrics, and the condition that selects paginated vs unpaginated reads.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools