Skip to main content
Glama

Appeak Pro: App Store Optimization

Check where an app ranks

check_keyword_ranks
Read-onlyIdempotent

Where an app ranks in the store's own search for up to 5 searches (top 50), with the apps on top. Without searches, checks the phrases its title and subtitle are written for.

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_url": "<store_url>"
    },
    "name": "check_keyword_ranks"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter store country (us, gb, de...). Defaults to the link's country, else us.
searchesNoSearches people type, e.g. ["budget planner", "expense tracker"]
store_urlYesThe app's App Store or Google Play link, e.g. https://apps.apple.com/us/app/id570060128

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value beyond them by disclosing result depth (top 50), the 5-search cap, that competitors appear in the output, and the fallback behavior when searches is omitted. It stops short of anything about quota, cost, or latency for what is an open-world lookup.

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 short sentences, front-loaded with the core outcome, with no filler. The clipped phrasing "with the apps on top" is slightly ambiguous about whether competitors are returned alongside the rank, costing a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explaining returns, and it only gestures at the shape (rank plus the apps above). For a low-complexity 3-parameter read tool this is mostly adequate, but an agent cannot fully anticipate the response structure or whether ranks are per-country.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns a bump by explaining what happens when searches is absent: the tool derives phrases from the title and subtitle rather than erroring. The store_url and country parameters are left to their schema text, which already documents defaults.

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 resource: it reports ranking positions for an app in store search results, capped at 5 searches and top 50, and names what comes back ("with the apps on top"). Clear enough to separate from check_metadata or audit_listing, though it never names a sibling or explicitly contrasts with check_ai_visibility, which is the nearest neighbor.

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?

Gives a concrete usage rule: pass up to 5 searches to check explicit phrases; omit searches to evaluate the phrases implied by the app's own title and subtitle. That default-behavior guidance is genuinely actionable, but there are no exclusions or pointers to which sibling to use when the agent wants visibility in AI assistants versus store search.

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.

Resources