Skip to main content
Glama
paulet4a-commits

WebDataTools Developer, app & research data MCP server

by paulet4a-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

google_play_scraper

Extract app metadata (title, developer, rating, price, installs, category, media) and reviews from Google Play for any package ID, URL, or search term, one row per app.

Instructions

Google Play Scraper returns app title, developer, rating, price, installs, category, media links, and optional reviews for any package id, Play Store URL or search term — one row per app. Billed to your own Apify account: ~$0.002 per app (Apify free-plan price, lower on paid plans).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appsYesApps — Enter the apps to scrape, one row is returned per app. Use the package id, e.g. com.spotify.music, a full Play Store URL, e.g. https://play.google.com/store/apps/details?id=com.spotify.music, or search:<term>, e.g. search:meditation, to scrape the top search results for a term. Example: ["com.spotify.music"].
countryNoCountry — Enter the 2-letter country code for the Play Store storefront to read, e.g. us, gb, de. Pricing, availability and installs shown can differ by country.us
languageNoLanguage — Enter the 2-letter language code for the app title, description and other text, e.g. en, es, de.en
searchLimitNoSearch result limit — Enter how many apps to return per search:<term> entry, e.g. 20. A single Play Store search page load returns roughly 20-30 unauthenticated results with no further pagination, so this is a ceiling, not a guarantee.
includeReviewsNoInclude reviews — Turn this on to add the newest reviews for each app (capped by "Max reviews per app"). Uses the same unauthenticated batchexecute endpoint the open-source google-play-scraper npm package uses for reviews — no login required, but it is an undocumented Google endpoint and could change without notice.
maxReviewsPerAppNoMax reviews per app — Enter how many of the newest reviews to fetch per app when "Include reviews" is on, e.g. 50. Ignored when "Include reviews" is off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: it discloses that the tool is billed to the caller's own Apify account at ~$0.002 per app, and that output is one row per app. It still omits auth prerequisites and failure/rate-limit behavior, but the cost disclosure is substantive value beyond structured data.

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, no filler, and the capability statement is front-loaded ahead of the pricing note. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description correctly takes on the return-value summary (field list) and the cost model. Parameters are fully covered by the schema. It is nearly complete, missing only auth/prerequisite details.

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 every parameter is already documented in the schema, including input formats, country/language codes, search limits and the reviews toggle. The description adds no syntax or semantics beyond that, which is the expected baseline 3.

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 (returns) and resource (Google Play app data), and enumerates the returned fields (title, developer, rating, price, installs, category, media links, reviews) plus the accepted input forms. The 'Google Play' resource inherently distinguishes it from the iOS-oriented sibling app_store_lookup.

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

Usage Guidelines2/5

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

The description never says when to pick this tool over alternatives, nor any prerequisites or exclusions. Input-format hints (package id / URL / search term) are parameter documentation, not usage guidance, so the agent gets no routing help.

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

Deploy Server

Other Tools