Skip to main content
Glama
storelift-mcp

storelift-mcp

Keyword rank history

get_history
Read-onlyIdempotent

Retrieve daily keyword rank history for an app in a selected country to track ranking changes and distinguish days the app was absent from top results.

Instructions

Keyword rank history for one country. Series points are [day, rank]; a null rank means the app was absent from the top results that day, which is not the same as a bad rank. How far back it reads follows the workspace's plan.

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": {
      "appId": "<appId>"
    },
    "name": "get_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesapp id from list_apps
countryNocountry code, e.g. tr, us (defaults to the app's first country)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • changedInput schema / properties / country / description
      Previous value: -"country code, e.g. tr, us"New value: +"country code, e.g. tr, us (defaults to the app's first country)"
  2. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding semantics the annotations cannot: null rank means the app was absent from top results rather than a poor rank, and the lookback window is governed by the workspace plan. Those are exactly the operational details an agent would otherwise misinterpret; only the return pagination/ordering is left unstated.

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 short sentences, front-loaded with what is returned, then the data-shape gotcha, then the retention constraint. Every sentence carries information an agent needs, with no restatement of the name or schema.

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 two-parameter read with full schema coverage and no output schema, this is close to sufficient: it explains return shape, the null semantics, and the retention boundary. Missing only guidance on which sibling to choose for current versus historical ranks.

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 description coverage is 100%, so appId and country are already documented, including the country default. The description adds only the single-country scoping constraint, not new syntax or format detail, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Keyword rank history for one country" names a specific resource and scope, and the [day, rank] series format tells an agent exactly what shape of data comes back. It stops short of distinguishing itself from rank-related siblings such as check_rank or hive_keyword_ranks, so an agent must infer that this is the historical/time-series variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the mention of series points and a plan-dependent lookback window signals a historical time-series call, but there is no explicit when-to-use, no exclusion of the current-rank or hive alternatives, and no statement of prerequisites beyond the plan limit.

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