AppSkyline

Check an app's keyword rank

get_keyword_rank

Read-onlyIdempotent

Use this when someone asks where their app ranks for a keyword right now in one store and country. Returns the app's live position, or not-ranked, after scanning the top 50 results by default and up to 200, and renders a rank card. Not for how a rank changed over time.

Input Schema

TableJSON Schema

Name	Required	Description
`num`	No	How many search results to scan for the app, from 1 to 200; defaults to 50
`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 to check, 1 to 200 characters
`appId`	Yes	AppSkyline app id (uuid)
`store`	Yes	Store to check: ios-app-store, macos-app-store, google-play or microsoft-store; the app needs an id on that store
`country`	No	Two-letter store country code such as US or IT; defaults to US

Output Schema

TableJSON Schema

Name	Required	Description
`app`	Yes
`lang`	Yes
`rank`	Yes	1-based position; null unless status is ranked
`term`	Yes
`store`	Yes
`status`	Yes
`country`	Yes
`resultsScanned`	Yes	How many results were scanned; report a rank as #N of this

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 28, 2026

changedInput schema / properties / appId / description

Previous value: -"Appskyline app id"New value: +"AppSkyline app id (uuid)"

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: -"How many results to scan when looking for the app (default 50, max 200)"New value: +"How many search results to scan for the app, from 1 to 200; defaults to 50"

changedInput schema / properties / store / description

Previous value: -"Which store to check"New value: +"Store to check: ios-app-store, macos-app-store, google-play or microsoft-store; the app needs an id on that store"

changedInput schema / properties / term / description

Previous value: -"Search term"New value: +"Search term to check, 1 to 200 characters"

addedOutput schema / properties / rank / description

Added value: +"1-based position; null unless status is ranked"

addedOutput schema / properties / resultsScanned / description

Added value: +"How many results were scanned; report a rank as #N of this"

First observedAug 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: it scans the top 50 by default, up to 200, and returns a live position or a not-ranked result, plus mentions rendering a rank card.

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 tight sentences with zero waste, front-loaded with the triggering condition and then the return behavior and exclusion. Every sentence earns its place.

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?

With a rich annotation set and an output schema present, the description need not explain the return payload; it nonetheless signals the rank-card rendering and the not-ranked case. Nothing an agent needs to invoke this correctly is missing.

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 six parameters (including defaults, enums and limits) are already documented in the schema. The description only restates the scan default and ceiling, adding no syntax or meaning beyond the structured fields.

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 specific verb (check/return) and resource (an app's live keyword rank) plus the scope (one store and country, right now). The final clause explicitly separates it from get_keyword_history, so an agent can distinguish it from the sibling without opening either schema.

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?

"Use this when someone asks where their app ranks for a keyword right now" gives a clear triggering context, and "Not for how a rank changed over time" supplies an explicit exclusion. It does not name get_keyword_history directly, so the routing is described rather than pinned to a sibling name.

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

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