Mine Google Play reviews for app bugs and feature requests
Pull Google Play reviews for an Android app as JSON, newest or by rating, to find bugs, complaints and feature requests after each release.
After every release, the first honest bug report often arrives as a one-star Google Play review. Product managers read the console a few reviews at a time, and a competitor's reviews are even harder to track. Lovely Router collects them in bulk. Send an app package name or Play Store link, get one JSON object per review, pay per review from a prepaid balance. Call it from a release checklist, a weekly report or an AI agent with one API key.
Hand it to your AI agent
Copy this prompt into Claude Code, Cursor, Codex or any coding agent. It tells the agent where the docs are and how to use your API key.
Mine Google Play reviews for app bugs and feature requests. Use the Lovely Router data tools: each returns JSON and is billed per result.
- Docs (read first): https://lovelyrouter.com/docs/tools/find.md and https://lovelyrouter.com/docs/tools/run.md
- Plan first: POST https://lovelyrouter.com/v1/tools/suggest with `{"task": "<my task in plain words>"}` (free). It returns the tools to run in order, each with an example `input`, the `input_required` fields, an estimated cost and a ready-made `run` request. Replace the example values with my task's; if a field is unclear, read the tool with GET https://lovelyrouter.com/v1/tools/<id>. To browse instead, POST https://lovelyrouter.com/v1/tools/discover searches the catalog.
- Show me the plan and its estimated cost (`total_est_cost_usd`) before running anything large.
- Run: POST https://lovelyrouter.com/v1/tools/<id>/run with `{"input": {...}, "max_results": N}`. A 200 has the finished run with `items`; a 202 means it is still running, so poll the `poll` path until `status` is `succeeded`, `failed`, `timed_out` or `stopped`.
- Only delivered results are billed. Keep max_results small on the first run, check the output, then scale up.
- If you support MCP, connect https://lovelyrouter.com/mcp instead (Streamable HTTP, same key; https://lovelyrouter.com/docs/tools/mcp.md) and use suggest_tools, get_tool and run_tool.
- Auth: read my API key from the LOVELY_API_KEY environment variable and send it as `Authorization: Bearer $LOVELY_API_KEY`. Never print or commit the key. If it is not set, ask me to create one at https://lovelyrouter.com/app/keys.
- Billing is prepaid: every call is charged to my balance, so test with a small request before running anything large.
- Every docs page is plain Markdown; the full index is https://lovelyrouter.com/llms.txt.
My task: <the inputs (links, keywords or accounts) and how many results you need>How it works
Identify the app
Use the package name, such as
com.supercell.brawlstars, or the full Google Play Store link of the app: yours or a competitor's.Run the tool with a cap
Send it to
POST /v1/tools/google-play-reviews/runwithmaxReviews,sortByandmax_results. The run holds its maximum cost from your balance and returns the reviews as JSON.Triage
Group reviews by theme: crashes, login, price, missing features. Compare with the last release to see whether a theme grew.
Get app reviews with one request
Google Play reviews takes one app in appIdOrUrl. maxReviews caps the reviews, and sortBy is newest, mostRelevant or rating:
curl https://lovelyrouter.com/v1/tools/google-play-reviews/run \
-H "Authorization: Bearer $LOVELY_API_KEY" \
-H "content-type: application/json" \
-d '{
"input": {
"appIdOrUrl": "com.supercell.brawlstars",
"maxReviews": 20,
"sortBy": "newest"
},
"max_results": 20
}'A run still going after 60 seconds returns 202; Run a tool shows how to poll. Pass language codes such as en, fr or de in language to filter reviews by language.
What each review holds
| Field group | What you get |
|---|---|
| Content | The review text |
| Rating | The stars given |
| Order | Sorted as you choose: newest, most relevant or by rating |
The tool returns Play Store reviews for one Android app per run. To compare apps, run each one.
Recipes
The morning after a release, pull the 100 newest reviews, count one-star reviews that mention the new version, and compare with the day before.
Collect 500 reviews, ask a model to extract every request of the form "I wish it could...", and rank them by how often they appear.
Run a rival's package name with sortBy set to rating, read the low-star themes, and add what they get wrong to your roadmap.
Filter by language to see whether bugs affect one market, for example only German reviews mention a payment failure.
Send new one- and two-star reviews to your helpdesk as tickets, so the team can reply and fix them.
Prefer plain words? Connect the MCP server and tell Claude Code or Cursor: "Pull the 200 newest Google Play reviews for this package name, group the complaints by theme and show the top five with two example quotes each. Set max_results to 200."
Pair it with other feedback sources
Android is half of most apps' users. The rest talk elsewhere:
Google Play Store reviews for an Android app.
Apple App Store reviews for an app ID and country.
Reddit posts for a query or subreddit: title, body, score, comments count, author, date.
Trustpilot reviews of a company by domain: stars, text, date, reply.
G2 reviews of a software product.
app-store-reviewsreturns Apple App Store reviews for an app ID and country.reddit-searchfinds posts that discuss your app, with score and comment count.trustpilot-reviewsreads reviews of your company by domain, with stars, text, date and reply.g2-reviewscovers software reviews, useful if your app also has a business version.
For all review sources together, see review monitoring.
What you pay
You pay per review: starting a run holds its maximum cost, the per-call fee plus the per-review fee times max_results, and the run settles to what it returned. The rest of the hold goes back to your balance. A run that fails or times out pays only for the reviews it delivered, and a run refused at the start costs nothing.
Pulling 200 reviews after each release is billed as 200 reviews per release. There is no subscription and no monthly minimum: top up from $5, and one balance pays for tools and models. The card above shows today's price; pricing lists every tool.
Frequently asked questions
What do I pass to identify the app?+
Either the package name, like com.supercell.brawlstars, or the full Google Play Store URL, in appIdOrUrl.
How many reviews can one run return?+
Up to 500 reviews per run. To go deeper, start several runs.
Can I get the newest reviews first?+
Yes. Set sortBy to newest. The other options are mostRelevant and rating.
Can I filter by language?+
Yes. language takes a list of language codes such as en, fr or de.
Can I read the reviews of several apps in one run?+
The input takes one app per run. Start one run for each app you want to compare.
Do I need a subscription?+
No. You add credit to a prepaid balance and each run draws it down. Failed runs pay only for the results they delivered, and nothing renews automatically.
Watching all review sources? See review monitoring, the tool catalog, and pricing.