Skip to main content
Glama

App category rank over time

app_category_rankings_history
Read-only

An app's position in a category chart across past days — the series to chart when asking whether an app is climbing or sliding. Costs 6 credits.

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": {
      "store": "<store>",
      "country": "<country>",
      "package": "<package>",
      "category": "<category>"
    },
    "name": "app_category_rankings_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of the most recent days to return, up to 365. 90 by default.
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
countryYesTwo-letter ISO country code, e.g. "US", "GB", "DE".
packageYesApp package / bundle id, e.g. "com.discord" (Android) or a numeric App Store id. If you only have the app name, call app_search first to resolve it.
categoryYesCategory tag from list_categories. Required.
sub_categoryNoChart inside the category: "topselling_free", "topgrossing", "topselling_paid" on Google Play; "top-free", "top-paid" on the App Store. list_categories has the valid tags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Category tag from list_categories."New value: +"Category tag from list_categories. Required."
    • changedInput schema / required
      Previous value: -[
      -  "store",
      -  "country",
      -  "package"
      -]New value: +[
      +  "store",
      +  "country",
      +  "package",
      +  "category"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuinely useful non-schema fact — the 6-credit cost — but says nothing about daily granularity, gaps in the series, or how missing days are represented, which matters for a time-series read.

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?

Two short sentences, front-loaded with the core definition before the use-case framing and cost. No repetition of schema content and nothing that could be cut without losing information.

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 read-only, flat 6-parameter tool with full schema documentation, the definition covers purpose, use-case and cost. The only real gap is the return shape — with no output schema, a note on whether the response is a date/rank series would have closed the loop.

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%, with limit, store, country, package, category and sub_category all self-documented, including the app_search and list_categories resolution hints. The description adds no parameter meaning beyond that, so the baseline 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?

States a specific verb+resource: an app's position in a category chart across past days, framed as a time series. It implicitly distinguishes itself from the snapshot siblings (app_category_rankings, app_category_rankings_single) via 'across past days', but never names them, so the differentiation is inferential rather than explicit.

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 clause 'the series to chart when asking whether an app is climbing or sliding' gives a clear use-case scenario, which is better than nothing. However, there is no explicit exclusion or routing guidance among the four closely related ranking siblings, leaving the agent to infer that this is the historical variant.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.