Skip to main content
Glama
Sign In

AppSkyline App Rankings

by com.appskyline
OverviewDiscussionsAdmin

Read recent Google Play reviews

list_google_play_reviews
Read-onlyIdempotent

Use this when someone asks what users say about their Android app on Google Play, or about recent ratings and complaints. Returns reviews with stars, text cut to 300 characters, app version, device, language and whether the developer replied, up to 100 per page. Google Play only returns reviews from the last 7 days. Not for App Store reviews.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appId": "<appId>"
    },
    "name": "list_google_play_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesAppSkyline app id (uuid); the app needs a Google Play service account in AppSkyline
tokenNonextPageToken from the previous page; absent for the first page
maxResultsNoReviews to return per page, from 1 to 100
translationLanguageNoTranslate review text into this language, such as en; omit to keep the original language

Output Schema

NameRequiredDescriptionDefault
appIdYes
statusYes
reviewsYesReviews created or edited in the last 7 days, as the Google Play API returns them; review text is cut to 300 characters
returnedYes
truncatedYes
nextPageTokenYesPass as token to get the next page; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / appId / description
      Previous value: -"Appskyline app id (uuid)"New value: +"AppSkyline app id (uuid); the app needs a Google Play service account in AppSkyline"
    • changedInput schema / properties / maxResults / description
      Previous value: -"How many reviews to fetch (max 100)"New value: +"Reviews to return per page, from 1 to 100"
    • changedInput schema / properties / token / description
      Previous value: -"Page token returned by a previous call"New value: +"nextPageToken from the previous page; absent for the first page"
    • changedInput schema / properties / translationLanguage / description
      Previous value: -"Translate review text into this language (e.g. en)"New value: +"Translate review text into this language, such as en; omit to keep the original language"
    • addedOutput schema / properties / nextPageToken / description
      Added value: +"Pass as token to get the next page; null on the last page"
    • addedOutput schema / properties / reviews / description
      Added value: +"Reviews created or edited in the last 7 days, as the Google Play API returns them; review text is cut to 300 characters"
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds one genuinely useful behavioral constraint not in the structured data: Google Play only returns reviews from the last 7 days, plus the 300-character truncation of review text. However, the return-field list partly restates what the output schema already provides, so this is a moderate add rather than a rich one.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the trigger and followed by return shape and the exclusion. Every sentence carries information, though the field enumeration is slightly list-heavy.

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?

With an output schema present, the description need not explain return values in depth; it covers purpose, trigger, exclusion, the 7-day retention limit and the page cap. Pagination via token is left to the schema, which is acceptable given full schema coverage.

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 the token/pagination and translationLanguage semantics. The description adds nothing parameter-specific beyond restating the 100-per-page cap, so baseline 3 applies.

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 and resource (list Google Play reviews) and immediately scopes it to Android/Google Play. It explicitly distinguishes itself from App Store reviews, so an agent can separate it from sibling store tools without opening a schema.

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

Usage Guidelines5/5

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

Opens with a concrete trigger ('when someone asks what users say about their Android app... or about recent ratings and complaints') and closes with an exclusion ('Not for App Store reviews'). Both the when and the when-not are explicit.

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

All AppSkyline App Rankings 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