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

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.

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 highlights — the user tags on this keyword. Each highlights entry is the same object list_rank_radar_tags returns (id, title, color, description, startAt, endAt, type, krtId, krtKeywordId); its id is the tagId the tag-management tools take. 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

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.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds substantial behavioral detail beyond that: the 90-day date constraint, pagination continuation via `hasNext`, response metadata fields, exclusion of paused keywords, the meaning of rank 101, and the structure and tag-management relevance of `highlights`.

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?

The description is long but well-structured and front-loads the core purpose, date constraints, and pagination behavior before field-level details. Most sentences earn their place, though the density is high and some schema-covered parameter details could be trimmed.

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 documenting the response shape, pagination metadata, keyword fields, rank semantics, and `highlights` object. It also covers prerequisites and sibling alternatives, making it complete for correct invocation.

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 the baseline is 3. The description adds useful pagination continuation guidance and maps `highlights.id` to the `tagId` used by tag-management tools, but it also conflicts with the schema defaults by saying that omitting `currentPage` and `pageSize` returns every active keyword, while the schema says these parameters default to 1 and 20 respectively.

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 description names a specific verb and resource: retrieving historical keyword ranking data for a Rank Radar within a date range. It also distinguishes itself from sibling tools by directing PPC metrics to `get_rank_radar_ppc_data` and Search Query Performance to `get_rank_radar_sqp_data`.

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?

It gives explicit usage context: analyze keyword ranking trends over time, requires startDate and endDate at most 90 days apart, and should be used after `list_rank_radars` to discover `rankRadarId`. It also names alternatives for PPC and SQP data and explains when to paginate for large Rank Radars.

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