Does this endpoint return historical Google Play rank time series for one app?

No. The Google Play feed is a live leaderboard snapshot. For install momentum on Android, Trends MCP exposes an app downloads keyword series that expects a package id. Treat charts as distribution signals and downloads as demand depth.

Why not scrape the public Play Store pages?

Public HTML changes often, captchas appear under load, and selectors break quietly. A managed JSON feed reduces maintenance and keeps automation stable enough for alerting and reporting.

How is this different from the App Store charts call?

App Store chart types are separate feed labels. Google Play is Android only. If the workflow needs both mobile ecosystems, schedule two calls and join on normalized titles in the downstream warehouse.

Google Play top charts REST API JSON

Mobile growth teams type blunt queries into the search bar: Google Play top charts API, Play Store rankings JSON, Android app chart API without scraping. The honest answer in many stacks is a patchwork of vendors, brittle scrapers, or manual exports.

Trends MCP exposes the live Google Play feed through the same POST https://api.trendsmcp.ai/api surface area as the rest of the catalog. The response is a ranked list with an as_of_ts timestamp so downstream jobs can version snapshots.

What the call returns

The handler expects mode set to top_trends and type set to Google Play exactly, including spacing and capitalization. The limit field defaults to 25 and can be raised to 200. Use offset when the REST layer supports pagination for that feed so weekly digests can walk past the first page without duplicating ranks.

The payload shape matches other live feeds: a data array of [rank, name] pairs, plus metadata fields such as count and type. Treat names as display strings; join to internal product catalogs with careful string normalization because store titles include subtitles and publisher suffixes.

Minimal request body

{
  "mode": "top_trends",
  "type": "Google Play",
  "limit": 50
}

Python example

import requests

res = requests.post(
    "https://api.trendsmcp.ai/api",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={"mode": "top_trends", "type": "Google Play", "limit": 50},
    timeout=30,
)
res.raise_for_status()
payload = res.json()

When charts alone mislead product teams

A rank jump proves visibility shifted. It does not prove revenue shifted, and it does not prove retention shifted. Pair the leaderboard with keyword style demand curves where they exist, for example Amazon product search interest for a companion hardware SKU, or Google Search interest for the brand string, or news volume around a launch window.

Trends MCP documents the full feed list and counting rules on the reference site. Start from https://trendsmcp.ai/docs when wiring quota budgets, because each feed page consumes quota on its own.

MCP clients and marketing automation

Cursor, Claude, Windsurf, VS Code, and other MCP hosts can call the same feed through the hosted MCP endpoint described in https://trendsmcp.ai/mcp-server-for-cursor. Prompt writers get better routing when they include the phrase via TrendsMCP so the client selects the tool instead of opening a generic web search.

For no-code chains, the REST shape is easy to hand to https://trendsmcp.ai/n8n-trends-mcp or https://trendsmcp.ai/make-com-trend-automation. Keep secrets in server side actions, never in browser side bundles.

Related reference pages

The iOS side of the same problem is documented on https://trendsmcp.ai/app-store-api. Broader mobile context lives on https://trendsmcp.ai/app-rankings and https://trendsmcp.ai/app-download-trends.

Google Play top charts API