Skip to main content
Glama
Sign In

AppmanAi

by com.appmanai
OverviewDiscussionsAdmin

Where apps entered a chart

app_category_start_rankings
Read-only

For each app given, the rank it first held in a chart from a start date — the baseline to measure a campaign against. Costs 5 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>",
      "packages": "<packages>"
    },
    "name": "app_category_start_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
countryYesTwo-letter ISO country code, e.g. "US", "GB", "DE".
categoryNoCategory tag from list_categories.
packagesYesPackage ids with a start date, up to 20, e.g. ["com.discord:2026-01-01"].
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful cost context ("Costs 5 credits"), which no structured field provides, but it says nothing about return format, per-package vs. aggregate behavior, or limits.

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 tight sentences with zero waste; the core behavior is front-loaded and the credit cost follows. Nothing to trim.

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 lookup with a fully described schema and no output schema, the description conveys the essential return value (the initial rank) and the cost. It could be clearer that the start date is embedded per package entry and how results are ordered, but it is largely sufficient to call the tool correctly.

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 (store, country, category, packages, sub_category) are fully documented in the schema. The description adds no syntax or format detail beyond it, 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 resource: returns the rank each given app first held in a chart (from a per-package start date), and frames it as a campaign baseline. This is fairly distinguishable from siblings like app_category_rankings_history, but it never names those alternatives, so the agent must infer the difference from the name alone.

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 baseline to measure a campaign against" implies a use case, but there is no explicit when-to-use, when-not-to-use, or pointer to sibling tools such as app_category_rankings or app_category_rankings_single. Usage is implied rather than stated.

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