Skip to main content
Glama

web-data-toolkit

by io.github.leekung125
OverviewDiscussionsAdmin

Google Play reviews for an Android app, by country and language.

google_play_reviews

Rating, text, author, thumbs-up count, app version and the developer's reply for any Google Play app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appYesGoogle Play URL or package name such as com.whatsapp.
maxNoMaximum reviews per app. Default 100.
rawNoReturn every field as JSON instead of a compact summary. Default false.
langNoLanguage code. Default en.
ratingNo1-5 to keep only that star rating.
countryNoTwo-letter country code. Default us.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / raw
      Added value: +{
+  "description": "Return every field as JSON instead of a compact summary. Default false.",
+  "type": "boolean"
+}
    • removedInput schema / raw
      Removed value: -{
-  "description": "Return every field as JSON instead of a compact summary. Default false.",
-  "type": "boolean"
-}
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists output fields but omits any mention of read-only nature, authentication, rate limits, pagination, or behavior on invalid inputs. The description does not contradict annotations (none exist) but fails to add meaningful behavioral context beyond the data fields.

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?

The description is a single, efficient sentence that front-loads the key output fields. There is no wasted text or redundancy. It is appropriately sized for a straightforward retrieval tool.

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

Completeness3/5

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

With six parameters and no output schema, the description should convey the output format (a list of reviews), sorting behavior, and how filters like country and language affect results. It only lists fields and does not mention that results are a list or that it honors the max and raw parameters beyond what the schema states. The description is adequate but leaves some operational details unspecified.

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 each parameter (app, max, raw, lang, rating, country) is already documented with defaults and meanings. The description adds no additional parameter semantics; it only enumerates return fields, which is useful but not param-specific. The baseline of 3 is appropriate given the schema's thoroughness.

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?

The description clearly identifies the resource (Google Play app reviews) and the specific data fields returned (rating, text, author, thumbs-up count, app version, developer's reply). The title reinforces the scope (Android apps, by country and language). It is easily distinguished from the sibling app_store_reviews, which targets Apple's App Store.

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

Usage Guidelines3/5

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

The description implies usage for Google Play apps but does not explicitly state when to use this tool versus alternatives like app_store_reviews. There is no 'use this when' or 'use that when' guidance, leaving the agent to infer from the name and title. The context is clear but not explicit.

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

All web-data-toolkit toolsInspect
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