Skip to main content
Glama

App rank for a keyword

keyword_app_metrics_rankings
Read-only

Where one app currently ranks in search results for one keyword. The direct answer to "am I ranking for this?". A rank of 0 means the app is not in the results. Costs 2 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
cacheNoUse a cached result. True by default; false re-checks the store live (~7s).
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
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

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, and the description adds genuinely useful context beyond them: rank 0 means 'not in results' (an output convention an agent can't infer) and 'Costs 2 credits' (a quota consideration absent from annotations). It doesn't say whether results are store-specific snapshots or how the cached vs live path differs beyond the schema note.

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?

Four short sentences, front-loaded with the purpose, then the use case, then the sentinel-value clarification, then cost. Every sentence earns its place.

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 correctly discharges the return-value burden by telling the agent what a 0 rank means, and it discloses cost. Minor gap: it doesn't say what else the response contains (e.g., whether only a rank integer is returned).

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 all five parameters (including cache default/latency and package resolution hint) are documented in the schema. The description adds no parameter-specific syntax or constraints, 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 and scope: 'Where one app currently ranks in search results for one keyword.' The 'one app / one keyword' framing implicitly distinguishes it from batch, worldwide, and history siblings, though it never names them.

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 direct answer to "am I ranking for this?"' gives a clear use context, but there is no explicit guidance on when to prefer this over keyword_app_metrics_rankings_batch, _history, or _worldwide, and no exclusions or prerequisites.

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.