Skip to main content
Glama
Hiru-ge
by Hiru-ge

Check App Store Search Ranking

asc_search_ranking
Read-onlyIdempotent

Check an app's search ranking for a keyword on the App Store. Optionally provide a bundle ID to find the rank of a specific app in search results.

Instructions

Check an app's search ranking for a keyword on the App Store, using the public iTunes Search API. No App Store Connect authentication (JWT) is required for this tool.

Args:

  • keyword (string, required): The search keyword

  • country (string): ISO 3166-1 alpha-2 country code (default 'jp')

  • bundleId (string, optional): Bundle ID of the target app. If provided, its rank within the top 200 results is looked up.

  • topN (number): Number of top results to include (default 10, max 50)

Returns: { "keyword": string, "country": string, "totalResults": number, "targetRank": number | null, // bundleId指定時にランクが見つかった場合のみ数値、それ以外はnull "targetNote": string | undefined, // targetRankがnullの場合の理由 "target": { // bundleIdが上位200件内で見つかった場合のみ "trackName": string, "averageUserRating": number, "userRatingCount": number } | undefined, "topResults": [ { "rank": number, "trackName": string, "bundleId": string, "averageUserRating": number, "userRatingCount": number, "price": number, "genres": string[] // 先頭2件のみ } ] }

Error Handling:

  • iTunes Search APIはレート制限(目安: 約20リクエスト/分)があり、超過するとHTTP 403が返ることがある。その場合は時間をおいて再試行すること。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNNoNumber of top-ranked results to include in the response (default 10, max 50).
countryNoISO 3166-1 alpha-2 country code (default 'jp').jp
keywordYesThe search keyword to check the ranking for.
bundleIdNoBundle ID of the target app. If provided, the tool looks up its rank within the search results (top 200).
Behavior5/5

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

Discloses the underlying API (iTunes Search), rate limits (~20 req/min), and HTTP 403 error handling. Annotations already mark readOnly, idempotent, non-destructive; description adds valuable behavioral context without contradiction.

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?

Well-structured: one-line summary, then special auth note, then parameter list, then return type in JSON, then error handling. No unnecessary words, front-loaded with purpose.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides full return schema example, error handling, and rate limit info. No output schema exists, but description compensates. Suitable for an agent to understand input, output, and constraints.

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?

All 4 parameters are described in the schema (100% coverage). The description adds extra meaning: bundleId triggers rank lookup among top 200, topN max is 50, country defaults to 'jp'. This goes beyond schema base.

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 clearly states the tool checks an app's search ranking for a keyword, using the public iTunes Search API. It distinguishes from sibling tools (most require App Store Connect auth) by noting no JWT is needed.

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?

Specifies no authentication required, which helps agents decide when to use. Mentions rate limits and error handling. Does not explicitly state when not to use or point to alternatives, but context makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hiru-ge/asc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server