Skip to main content
Glama
Data-Dive-Tools

DataDive MCP

Official
by Data-Dive-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Rank Radars

list_rank_radars
Read-only

Retrieves a paginated list of Rank Radars—keyword-rank trackers for ASINs—so you can find a rankRadarId before fetching its data. Filter by niche, spaces, labels, status, or search text.

Instructions

Use this to find a rankRadarId before calling get_rank_radar_data. Filter by nicheId if the user has already identified a niche, or by spaces / labels (ids from list_spaces / list_labels), which match through the Rank Radar's niche. Retrieves a paginated list of Rank Radars — keyword-rank trackers monitoring organic and sponsored positions for specific ASINs over time. Each item includes id, status (ACTIVE, PAUSED or ARCHIVED), asin, marketplace, keywordCount, title, imageUrl, and summary metrics: top10KW, top10SV, top50KW, top50SV. Supports pagination metadata (currentPage, pageSize, total, lastPage, hasNext, hasPrev); a page holds at most 50 Rank Radars, so a large account needs several calls.

Input Schema

NameRequiredDescriptionDefault
labelsNoOnly Rank Radars whose niche has at least one of these labels (ids from `list_labels`, up to 100). Combines with `spaces` and the other filters with AND.
spacesNoOnly Rank Radars whose niche is in at least one of these Spaces (ids from `list_spaces`, up to 100). Combines with `labels` and the other filters with AND.
statusNoWhich Rank Radars to return. ACTIVE (the default) are tracking; PAUSED have been stopped but keep their history and can be resumed; ARCHIVED have been deleted; ALL means active and paused together. Archived Rank Radars are returned only by an explicit ARCHIVED.
nicheIdNoFilter Rank Radars by Niche identifier. Use after `list_niches`.
pageSizeNoItems per page (max 50). Defaults to 20.
searchTextNoFilter Rank Radars by ASIN or product title.
currentPageNoPage number, 1-indexed. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.20.1
    • addedInput schema / properties / labels
      Added value: +{
+  "description": "Only Rank Radars whose niche has at least one of these labels (ids from `list_labels`, up to 100). Combines with `spaces` and the other filters with AND.",
+  "items": {
+    "minimum": 1,
+    "type": "integer"
+  },
+  "maxItems": 100,
+  "type": "array"
+}
    • addedInput schema / properties / spaces
      Added value: +{
+  "description": "Only Rank Radars whose niche is in at least one of these Spaces (ids from `list_spaces`, up to 100). Combines with `labels` and the other filters with AND.",
+  "items": {
+    "minimum": 1,
+    "type": "integer"
+  },
+  "maxItems": 100,
+  "type": "array"
+}
  2. Changed4 schema fields changedv0.11.0
    • changedInput schema / properties / pageSize / description
      Previous value: -"Items per page (max 100). Defaults to 20."New value: +"Items per page (max 50). Defaults to 20."
    • changedInput schema / properties / pageSize / maximum
      Previous value: -100New value: +50
    • changedInput schema / properties / status / description
      Previous value: -"Filter by Rank Radar status. By default, returns only ACTIVE Rank Radars. Allowed: ACTIVE, PAUSED, ARCHIVED."New value: +"Which Rank Radars to return. ACTIVE (the default) are tracking; PAUSED have been stopped but keep their history and can be resumed; ARCHIVED have been deleted; ALL means active and paused together. Archived Rank Radars are returned only by an explicit ARCHIVED."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "ACTIVE",
-  "PAUSED",
-  "ARCHIVED"
-]New value: +[
+  "ACTIVE",
+  "PAUSED",
+  "ARCHIVED",
+  "ALL"
+]
  3. First observedv0.8.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the weight and does it well: it discloses pagination metadata fields, the hard 50-item page cap, and warns that a large account needs several calls. The status semantics (ACTIVE/PAUSED/ARCHIVED, archived only on explicit request) largely repeat the schema, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the downstream call are front-loaded in the first clause, filters come next, and return/pagination details come last. The single paragraph is dense but every sentence carries routing or shape information an agent needs.

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 enumerated item fields (id, status, asin, marketplace, keywordCount, title, imageUrl, top10KW/SV, top50KW/SV) and pagination fields fully describe what comes back. Combined with the 50-per-page cap note, nothing needed to call it correctly or interpret results is missing.

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 baseline is 3; the description still adds value by explaining that spaces/labels filter indirectly 'through the Rank Radar's niche' and by chaining parameter sources to list_spaces/list_labels/list_niches. The pageSize/currentPage details are duplicative of 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 verb+resource ('Retrieves a paginated list of Rank Radars') and defines what a Rank Radar is (keyword-rank trackers for ASINs over time), which no sibling name alone conveys. It explicitly positions itself against get_rank_radar_data and get_rank_radar_data as a downstream consumer.

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?

Explicit when-to-use: 'Use this to find a rankRadarId before calling get_rank_radar_data.' It also routes the two filtering paths concretely ('by nicheId if the user has already identified a niche', or by spaces/labels with ids from list_spaces/list_labels), so the agent knows both the purpose and the prerequisite lookups.

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