Skip to main content
Glama
storelift-mcp

storelift-mcp

Chart positions

get_charts
Read-onlyIdempotent

Retrieve App Store chart positions for one country, including current ranks by free, paid, grossing, overall and category lists, plus rank history.

Instructions

App Store chart position for one country: current ranks per list (free / paid / grossing, overall and in category) plus their history. Google Play is absent on purpose — it has no public top chart, and a number here would be invented.

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_charts"
  }
}

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.7/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 bar is lower. The description adds genuine value beyond that: it enumerates what is returned (per-list ranks, overall and in-category, plus historical values) and explicitly discloses a coverage limitation — Google Play data is deliberately absent — which prevents an agent from expecting or fabricating a cross-store result.

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?

Two sentences, front-loaded with what the tool returns before the caveat. The Google Play sentence is slightly conversational ('a number here would be invented') but earns its place by preventing a wrong assumption.

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?

There is no output schema, so the description carries the burden of indicating the return shape, which it does at a summary level (ranks per list, overall and category, plus history). Missing only details such as result structure or history depth, which are minor for a low-risk read tool.

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%, with appId sourced 'from list_apps' and country documented including its default to the app's first country, so the baseline is 3. The description only restates that the result is scoped to a single country and adds no format or validation detail beyond the schema.

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?

States a specific verb/resource (retrieve App Store chart positions) with precise scope: one country, ranks per list (free/paid/grossing, overall and category) plus history. It does not name sibling tools such as get_chart_movers or market_charts, so differentiation is inferred from 'current ranks ... plus their history' rather than stated.

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?

The one-country scope and the explicit exclusion of Google Play imply when this tool is appropriate and when it is not, which is useful. However, there is no explicit routing guidance to alternatives like get_chart_movers or market_charts, nor any stated prerequisites for calling it.

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