Skip to main content
Glama

App rank history for a keyword

keyword_app_metrics_rankings_history
Read-only

One app's rank for a keyword over time — the series to chart when asking whether a change helped. Pick the window with period. A rank of 0 means the app is not in the results. 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>",
      "keyword": "<keyword>"
    },
    "name": "keyword_app_metrics_rankings_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
periodNoWindow to report. Month by default.
countryYesTwo-letter ISO country code, e.g. "US", "GB", "DE".
keywordYesA single search term, e.g. "habit tracker".
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses two genuinely useful traits: a rank of 0 means the app is absent from results (a data-semantics trap), and the call costs 6 credits (budget awareness). It does not say what the series granularity or length looks like for each period, which is the remaining behavioral unknown.

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 the tool returns, then the control, then the caveat and cost. No sentence is redundant or out of order.

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?

With no output schema, the description still covers the key interpretation rule (0 = not ranked) and the credit cost, which is what an agent most needs. It leaves the shape of the returned series (number of points, resolution within week/month/year) unexplained, a minor but real gap for a charting 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%, so all five parameters are already documented, including the period enum and the package-id fallback to app_search. The description's only addition is reinforcing `period` as the window selector, which adds little beyond the schema; 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?

"One app's rank for a keyword over time" names a specific verb-resource-scope, and the "over time" framing implicitly separates it from the snapshot sibling keyword_app_metrics_rankings. It stops short of naming the alternatives (current ranking, batch, worldwide), so an agent must infer the boundary rather than being told it.

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?

"the series to chart when asking whether a change helped" gives a concrete usage scenario, and "Pick the window with `period`" points at the controlling parameter. There is no when-not-to-use guidance and no sibling tool is named for the current-snapshot case, so it is clear context without exclusions.

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.