AppSkyline App Rankings

Search an app store

search_store_results

Read-onlyIdempotent

Use this when someone asks which apps show up for a search term, or who their competitors are for a keyword, on the App Store, Mac App Store, Google Play or Microsoft Store. Returns the live results in rank order with store id, title, rating and developer (10 by default, up to 200). Not for one app's own position.

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

Input Schema

Name	Required	Description
`num`	No	Number of results to return, from 1 to 200; defaults to 10
`lang`	No	Two-letter language code such as en or it; defaults to en except on Google Play, which uses the store default
`term`	Yes	Search term as a user would type it in the store, 1 to 200 characters
`store`	Yes	Store to search: ios-app-store, macos-app-store, google-play or microsoft-store
`country`	No	Two-letter store country code such as US or IT; defaults to US

Output Schema

Name	Required	Description
`lang`	Yes
`term`	Yes
`store`	Yes
`status`	Yes
`country`	Yes
`results`	Yes	Live search results in store rank order; nothing is stored in AppSkyline
`truncated`	Yes	True when the store returned more than 200 results

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 28, 2026

changedInput schema / properties / country / description

Previous value: -"Two-letter country code (e.g. US, IT)"New value: +"Two-letter store country code such as US or IT; defaults to US"

changedInput schema / properties / lang / description

Previous value: -"Two-letter language code (e.g. en, it)"New value: +"Two-letter language code such as en or it; defaults to en except on Google Play, which uses the store default"

changedInput schema / properties / num / description

Previous value: -"Number of results to return (default depends on store)"New value: +"Number of results to return, from 1 to 200; defaults to 10"

changedInput schema / properties / store / description

Previous value: -"Which store to search"New value: +"Store to search: ios-app-store, macos-app-store, google-play or microsoft-store"

changedInput schema / properties / term / description

Previous value: -"Search term"New value: +"Search term as a user would type it in the store, 1 to 200 characters"

addedOutput schema / properties / results / description

Added value: +"Live search results in store rank order; nothing is stored in AppSkyline"

addedOutput schema / properties / results / items / properties / score / description
```
Added value: +"Rating score as the store reports it"
```

addedOutput schema / properties / truncated / description

Added value: +"True when the store returned more than 200 results"

First observedAug 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond them: results come back in rank order with specific fields, are live, and default to 10 with a ceiling of 200.

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 usage trigger front-loaded and the return shape and exclusion packed into the second. Nothing is repeated.

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?

For a five-parameter read tool with an output schema, annotations and a full schema description coverage, all that is needed to select and invoke it is present: when to use, when not to, or which stores, and result-size bounds.

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 store, term, num, lang and country are all documented in the schema itself. The description only restates the num default (10, up to 200) and the store list, which duplicates schema content rather than adding syntax or format guidance, so the baseline 3 applies.

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?

States a precise verb+resource ('search' an app store) and enumerates the four supported stores, immediate scope. Naming the exact question it answers ('which apps show up for a search term') separates it cleanly from siblings like get_store_listing and get_app.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit positive trigger ('when someone asks which apps show up for a search term, or who their competitors are for a keyword') plus an explicit exclusion ('Not for one app's own position'), which routes the agent away from this tool for single-app lookups.

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

All AppSkyline App Rankings 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?