Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

google-play-details

Retrieve comprehensive Google Play app data including ratings, installs, pricing, developer details, and version information for market analysis and competitor research.

Instructions

Get detailed information about a Google Play app. Returns an object with:

  • title: App name

  • description: Full app description

  • descriptionHTML: Description with HTML formatting

  • summary: Short description

  • installs: Install count range

  • minInstalls: Minimum install count

  • maxInstalls: Maximum install count

  • score: Average rating (0-5)

  • scoreText: Rating display text

  • ratings: Total number of ratings

  • reviews: Total number of reviews

  • histogram: Rating distribution by star level

  • price: Price in local currency

  • free: Boolean indicating if app is free

  • currency: Price currency code

  • priceText: Formatted price string

  • offersIAP: Boolean indicating in-app purchases

  • IAPRange: Price range for in-app purchases

  • androidVersion: Minimum Android version required

  • androidVersionText: Formatted Android version text

  • developer: Developer name

  • developerId: Developer ID

  • developerEmail: Developer contact email

  • developerWebsite: Developer website URL

  • developerAddress: Developer physical address

  • genre: App category

  • genreId: Category ID

  • icon: Icon URL

  • headerImage: Feature graphic URL

  • screenshots: Array of screenshot URLs

  • contentRating: Content rating (e.g. 'Everyone')

  • contentRatingDescription: Content rating details

  • adSupported: Boolean indicating if app shows ads

  • released: Release date

  • updated: Last update date

  • version: Current version string

  • recentChanges: Latest version changes

  • preregister: Boolean indicating if app is in pre-registration

  • editorsChoice: Boolean indicating Editor's Choice status

  • features: Array of special features

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesGoogle Play package name (e.g., 'com.google.android.apps.translate')
langNoLanguage code for result text (default: en)en
countryNoCountry code to check app availability (default: us)us

Implementation Reference

  • Handler function that executes the tool logic: fetches Google Play app details using the gplay library and returns the JSON-stringified result wrapped in MCP content format.
    async ({ appId, lang, country }) => {
      const details = await gplay.app({ appId, lang, country });
      return { content: [{ type: "text", text: JSON.stringify(details) }] };
    }
  • Zod schema for input validation, defining parameters appId (required string), lang and country (optional strings with defaults).
    {
      appId: z.string().describe("Google Play package name (e.g., 'com.google.android.apps.translate')"),
      lang: z.string().default("en").describe("Language code for result text (default: en)"),
      country: z.string().default("us").describe("Country code to check app availability (default: us)")
    }, 
  • src/server.js:426-477 (registration)
    Registration of the 'google-play-details' tool with server.tool, providing the tool name, detailed description string, input schema, and handler function.
    server.tool("google-play-details", 
      "Get detailed information about a Google Play app. Returns an object with:\n" +
      "- title: App name\n" +
      "- description: Full app description\n" +
      "- descriptionHTML: Description with HTML formatting\n" +
      "- summary: Short description\n" +
      "- installs: Install count range\n" +
      "- minInstalls: Minimum install count\n" +
      "- maxInstalls: Maximum install count\n" +
      "- score: Average rating (0-5)\n" +
      "- scoreText: Rating display text\n" +
      "- ratings: Total number of ratings\n" +
      "- reviews: Total number of reviews\n" +
      "- histogram: Rating distribution by star level\n" +
      "- price: Price in local currency\n" +
      "- free: Boolean indicating if app is free\n" +
      "- currency: Price currency code\n" +
      "- priceText: Formatted price string\n" +
      "- offersIAP: Boolean indicating in-app purchases\n" +
      "- IAPRange: Price range for in-app purchases\n" +
      "- androidVersion: Minimum Android version required\n" +
      "- androidVersionText: Formatted Android version text\n" +
      "- developer: Developer name\n" +
      "- developerId: Developer ID\n" +
      "- developerEmail: Developer contact email\n" +
      "- developerWebsite: Developer website URL\n" +
      "- developerAddress: Developer physical address\n" +
      "- genre: App category\n" +
      "- genreId: Category ID\n" +
      "- icon: Icon URL\n" +
      "- headerImage: Feature graphic URL\n" +
      "- screenshots: Array of screenshot URLs\n" +
      "- contentRating: Content rating (e.g. 'Everyone')\n" +
      "- contentRatingDescription: Content rating details\n" +
      "- adSupported: Boolean indicating if app shows ads\n" +
      "- released: Release date\n" +
      "- updated: Last update date\n" +
      "- version: Current version string\n" +
      "- recentChanges: Latest version changes\n" +
      "- preregister: Boolean indicating if app is in pre-registration\n" +
      "- editorsChoice: Boolean indicating Editor's Choice status\n" +
      "- features: Array of special features",
      {
        appId: z.string().describe("Google Play package name (e.g., 'com.google.android.apps.translate')"),
        lang: z.string().default("en").describe("Language code for result text (default: en)"),
        country: z.string().default("us").describe("Country code to check app availability (default: us)")
      }, 
      async ({ appId, lang, country }) => {
        const details = await gplay.app({ appId, lang, country });
        return { content: [{ type: "text", text: JSON.stringify(details) }] };
      }
    );
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 return fields but does not mention critical behaviors like rate limits, authentication requirements, error conditions, or data freshness. For a tool with no annotations, this is a significant gap in transparency.

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?

The description is well-structured and front-loaded with the core purpose, followed by a detailed list of return fields. While lengthy due to the exhaustive field enumeration, every sentence serves a purpose—clarifying the output structure. Some redundancy in field descriptions (e.g., 'Boolean indicating...') could be trimmed for efficiency.

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?

Given the tool's complexity (3 parameters, no output schema, no annotations), the description is moderately complete. It thoroughly documents the return format, which compensates for the lack of output schema. However, it misses behavioral context (e.g., error handling, rate limits) and usage guidelines, leaving gaps for the agent.

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?

The input schema has 100% description coverage, clearly documenting the three parameters (appId, lang, country). The description adds no additional parameter information beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get detailed information about a Google Play app.' It specifies the verb ('Get') and resource ('Google Play app'), making the function unambiguous. However, it does not explicitly differentiate from sibling tools like 'google-play-search' or 'google-play-developer', which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools available (e.g., 'google-play-search', 'google-play-developer', 'google-play-reviews'), there is no indication of context, prerequisites, or exclusions. This leaves the agent without direction on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JiantaoFu/AppInsightMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server