Store rank is a relative signal. Source app rankings expects Android package identifiers so assistants chart whether an app is gaining or losing leaderboard position without confusing marketing names from the Play Store listing.
A product team can add users while sliding down a category leaderboard. Competitors may be growing faster even when absolute installs look healthy. Trends MCP documents source: "app rankings" under Data sources with the Android bundle id requirement spelled out.
Users often name apps by marketing title. Assistants should request the Play Store URL or bundle id before invoking get_trends or get_growth. The id parameter in play.google.com/store/apps/details?id=com.example.app is the keyword.
If the user only cares about today's chart leaders, route to get_top_trends with type Google Play or App Store Top Free instead of historical rankings.
Competitive benchmark. A growth PM pastes two competitor Play Store links. The assistant extracts both bundle ids, calls get_growth with percent_growth: ['3M', '12M'] for each, and reports which app gained chart position faster.
Release post-mortem. After a version ship, the assistant compares a custom growth window (recent vs baseline dates) on app rankings, then repeats the same window on app downloads to see whether chart gains came with install acceleration.
Investor prep. Before a mobile earnings call, the assistant charts 12-month ranking history for the target bundle id and flags any quarter where rank improved while downloads stalled, a pattern that often precedes paid user acquisition spend.
The app downloads assistant page covers install velocity by the same bundle id. Rankings answer "are we beating rivals on the store?" Downloads answer "are installs still accelerating?" Assistants should call both when the user's question mixes competitive standing with growth rate.
For REST payloads and response fields, see the app rankings API.
App rankings data source, App download trends for assistants, App growth intelligence. Hub: MCP trend tools for assistants.
Tools for this workflow
get_trendsPlot chart position history for a mobile product across quarters.
get_trends(keyword='com.spotify.music', source='app rankings', data_mode='weekly')get_growthScore whether an app improved on Play charts after a release or campaign.
get_growth(keyword='com.duolingo', source='app rankings', percent_growth=['1M', '3M', '12M'])get_top_trendsRead current Google Play or App Store chart leaders for live mobile context.
get_top_trends(type='Google Play', limit=25)FAQ