Skip to main content
Glama
storelift-mcp

storelift-mcp

Search results by day

hive_keyword_ranks
Read-onlyIdempotent

Retrieve daily App Store or Google Play keyword rankings as ordered app IDs with rating counts for a chosen storefront, platform, search term, and date range.

Instructions

Who ranks where for any search term in one storefront, day by day: the ordered app ids in that storefront's search results, each with its rating count. One call returns up to 1,000 rows (days × depth); pass the ids to hive_app_details for names. 10 credits for up to 7 days, 20 for up to 30, 40 for up to 90.

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": {
      "term": "<term>"
    },
    "name": "hive_keyword_ranks"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoresults per day, up to 200 (default 50)
daysNodays back, up to 90 (default 7)
termYessearch term, e.g. habit tracker
countryNostorefront code, e.g. us (defaults to us)
platformNodefaults to ios

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds behavior they cannot express: a hard cap of 1,000 rows per call, the days × depth relationship that can hit that cap, and explicit credit costs by window. These are exactly the operating constraints an agent needs before spending credits.

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?

Three sentences, front-loaded with what the tool returns, then the row cap and follow-on tool, then pricing. Nothing repeats the schema verbatim and nothing is padded.

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?

There is no output schema, yet the description still explains the return shape (ordered ids plus rating counts), the volume ceiling, and how to hydrate names. For a read-only ranking query with full schema coverage, nothing material is missing.

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 top, days, term, country, and platform are already documented, giving a baseline of 3. The description adds useful framing (row count is days × depth, and days drives the credit tier) but no syntax or defaults beyond 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?

The description names a specific resource and verb: the ordered app ids that appear in one storefront's search results for a term, day by day, each with its rating count. It also distinguishes itself from hive_app_details, which it says to use for names rather than for the ranking data itself.

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?

It explicitly routes name resolution to hive_app_details and makes the cost/days tradeoff visible ('10 credits for up to 7 days, 20 for up to 30, 40 for up to 90'), which tells an agent when to extend the window. It does not contrast with hive_keyword_spy or hive_keyword_metrics, so the sibling selection is only partly guided.

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