Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_app

Fetch full Google Play app details by package name, including installs, ratings, pricing, version, developer, media, comments, and recommendations.

Instructions

Retrieve full Google Play app details. Returns app metadata from a Google Play details page, including installs, ratings, pricing, version info, developer metadata, media assets, release state, selected user comments, and "More by this developer" and "Similar apps" recommendation rails. For a per-device (phone/tablet/Chromebook) ratings-and-reviews breakdown, see /googleplay/ratings. Defaults: country=us, lang=en.

Input Schema

NameRequiredDescriptionDefault
langNoTwo-letter language code
app_idYesGoogle Play package name
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/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, and it does meaningfully disclose the returned data shape (installs, ratings, pricing, media assets, recommendation rails) plus locale defaults. It omits auth requirements, rate limits, and pagination behavior, so it is good but not exhaustive for an unannotated tool.

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?

Front-loads the core purpose, then the return contents, then the sibling redirect and defaults. Efficient and well ordered, though the long enumeration of returned fields is somewhat dense.

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 no output schema and no annotations, the description supplies the return-value inventory and locale defaults that an agent would otherwise lack. It is largely complete, with only operational details (auth, rate limits, pagination) missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value beyond the schema by declaring the default values country=us and lang=en, which the schema does not specify. app_id is left to the schema's own definition.

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 (Retrieve) and resource (Google Play app details) and enumerates what the response contains. It distinguishes itself from the sibling googleplay_ratings by pointing to that tool for a per-device breakdown.

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

Usage Guidelines4/5

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

Explicitly routes the agent to /googleplay/ratings when per-device ratings/reviews are wanted, giving a clear when-to-use-this-vs-that condition. However, it says nothing about how it relates to other close siblings like googleplay_search, googleplay_reviews, googleplay_similar, or googleplay_developer.

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