Skip to main content
Glama
Sign In
@applyra/mcp-server

@applyra/mcp-server

by applyra-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get store top charts

top_charts
Read-only

Retrieve App Store or Google Play top-chart rankings by country, category, and collection, including daily rank movement for tracking ASO performance.

Instructions

Get a store top-chart ranking (App Store or Google Play) for a country, category and collection, with daily rank movement. Returns the snapshot date and ranked apps (rank, app_id, apple_id, title, developer, icon, rating, price, currency, delta vs. yesterday, is_new). Category: pass "OVERALL" (default) for the overall chart, or a store category value (iTunes genre id e.g. "6014" for Games, or a Google Play category e.g. "GAME"). Collection: free (default), paid, or grossing.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (1 to 100, default 100: charts cover the top 100 on both stores)
storeYesApp store: GPLAY (Google Play) or ITUNES (App Store)
countryYesISO country code (e.g., US, FR, DE)
categoryNoCategory key: "OVERALL" (default) or a store category value (iTunes genre id e.g. "6014", Google Play category e.g. "GAME")
collectionNoChart type: free (default), paid, or grossing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows to return (max 200, default 100)"New value: +"Max rows to return (1 to 100, default 100: charts cover the top 100 on both stores)"
  2. Changed1 schema field changedv1.6.1
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context by describing the returned data, including daily rank movement, snapshot date, and the specific fields (e.g., delta vs. yesterday, is_new), which matters because no output schema is provided.

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?

The description is front-loaded with the core purpose in the first sentence, followed by useful return-field and parameter details. The long parenthetical list of returned fields is slightly dense, but it earns its place because there is no output schema to document the response.

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?

Given the lack of an output schema, the description helpfully enumerates the returned fields and explains the category and collection semantics. It does not mention the limit parameter or how to discover valid category values (e.g., via list_top_chart_categories), but those gaps are minor because the schema covers parameter details and the core return behavior is described.

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 the schema already documents all five parameters. The description largely repeats the schema's parameter descriptions, including the same examples (iTunes genre id '6014', Google Play category 'GAME') and defaults (OVERALL, free), adding no meaningful semantic detail beyond what the structured schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: retrieving a store top-chart ranking for a given country, category, and collection. It names the two stores (App Store or Google Play) and the chart types, which distinguishes it from sibling tools like list_top_chart_categories and the keyword-rank-history tools.

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 description implies the tool's use case (fetching a top-chart ranking) and provides parameter defaults, but it does not explicitly state when to choose this tool over alternatives or when not to use it. No sibling tool is named as an alternative, so the guidance remains implicit.

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

Deploy Server

Other Tools