Skip to main content
Glama

AppSkyline

by com.appskyline.mcp
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.

Input Schema

TableJSON 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

TableJSON 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.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a hard 7-day retention window on Google Play's side and 300-character truncation of review text. It does not mention rate limits or what happens when a page token expires, which keeps it short of a 5.

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?

Three sentences, front-loaded with the usage trigger, then return shape, then the platform constraint and exclusion. Every sentence carries distinct information and nothing is repeated from the schema.

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

Completeness5/5

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

With annotations covering safety, a full input schema and an output schema, the description only needs to supply routing, retention limits and truncation behavior — which it does. An agent has everything required to call this correctly and interpret the result.

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 appId, token, maxResults and translationLanguage are already fully documented in the schema. The description only restates the page size ('up to 100 per page') and implies the pagination flow, adding no syntax or format detail beyond structured fields. 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 and resource (read Google Play reviews) and immediately distinguishes itself from the nearest lookalike with 'Not for App Store reviews.' It also enumerates the exact payload (stars, truncated text, app version, device, language, developer reply), so an agent knows what it gets without opening the output 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?

Gives an explicit trigger ('when someone asks what users say about their Android app on Google Play, or about recent ratings and complaints') plus an explicit when-not ('Not for App Store reviews'). No relevant competing sibling exists in the tool list, so no further routing is needed.

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

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