AppTrack Ninja

App chart positions

get_app_ranks

Read-onlyIdempotent

Overall and category chart positions of one app in one storefront: today, the move over 7 days and the best in the window. Pro adds the daily series (days up to 90).

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>",
      "country": "<country>"
    },
    "name": "get_app_ranks"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`appId`	Yes
`country`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

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 real value beyond them by disclosing the payload shape (today's rank, 7-day move, best in window) and a plan-level gating rule (Pro unlocks the daily series), which an agent needs in order to interpret a thin response.

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 sentences, zero filler, with the core deliverable front-loaded and the plan-dependent variation placed second. Nothing is repeated from the schema or annotations.

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, and while the description sketches the returned metrics it does not say what the fields look like, what happens when days is omitted, or whether non-Pro callers get truncated results or an error. Adequate to attempt the call, incomplete for interpreting or handling edge cases.

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 0%, so the description must carry parameter meaning, and it only does so partially. 'Days up to 90' clarifies the days parameter's purpose and cap, and 'one app in one storefront' loosely maps to appId and country, but no format hints (numeric app ID, two-letter country code) or default value for days are given.

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?

The description names the resource and scope precisely: overall and category chart positions for one app in one storefront. An agent can tell this apart from get_app_estimates or get_app_market by the 'chart positions' framing, though no sibling is referenced by name and the retrieval verb is only implied.

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?

Usage is implied rather than stated: you call it when you need rank data for one app in one storefront. The only conditional guidance is the Pro note ('Pro adds the daily series'), which ties to the days parameter but does not explain when to choose this over sibling tools or what an agent should do if it lacks Pro access.

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

All AppTrack Ninja tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?