Skip to main content
Glama
Sign In

AppmanAi

by com.appmanai
OverviewDiscussionsAdmin

App ranks across category charts

app_category_rankings
Read-only

List every category chart an app currently appears in, with its rank in each. The place to start when you do not already know which chart matters. Costs 3 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>"
    },
    "name": "app_category_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows to return, up to 100.
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.
categoryNoCategory tag from list_categories.
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. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only/open-world profile, so the description earns credit for adding what they don't: a concrete cost of 3 credits, which lets an agent budget calls. "Currently appears in" also signals a point-in-time snapshot rather than history. It doesn't describe pagination or the row shape, but that's a minor gap given annotations.

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, zero filler, with the core action first and the usage cue and cost trailing. Nothing restates the name or title.

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 listing with a fully documented schema, the description covers purpose, entry-point guidance, and credit cost. Since there's no output schema, a brief note on what a row contains beyond rank would close the remaining gap.

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 every parameter including store, country, package, category, and sub_category is already documented, down to the package-resolution hint pointing at app_search. The description adds no parameter-level meaning beyond what the schema provides, 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?

"List every category chart an app currently appears in, with its rank in each" gives a specific verb, resource, and return shape. The word "every" plus "currently" implicitly separates it from the _single (one chart) and _history (over time) 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"The place to start when you do not already know which chart matters" gives a clear entry-point condition, which strongly implies the single-chart sibling should be used once the chart is known. It stops short of naming that alternative or stating any exclusions explicitly.

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

All AppmanAi toolsInspect
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