Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

google-play-search

Search Google Play Store apps to research competitors, analyze market trends, and gather app intelligence with detailed results including ratings, pricing, and developer information.

Instructions

Search for apps on Google Play. Returns a list of apps with:

  • title: App name

  • appId: Package name (e.g. 'com.company.app')

  • url: Play Store URL

  • icon: Icon image URL

  • developer: Developer name

  • developerId: Developer ID

  • priceText: Price display text

  • free: Boolean indicating if app is free

  • summary: Short description

  • scoreText: Rating display text

  • score: Rating (0-5)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term to query apps
priceNoFilter by price: all, free, or paid (default: all)all
numNoNumber of results to retrieve (default: 20, max: 250)
langNoLanguage code for result text (default: en)en
countryNoCountry code to get results from (default: us)us
fullDetailNoInclude full app details in results (default: false)

Implementation Reference

  • The handler function for the 'google-play-search' tool. It destructures the input parameters and calls gplay.search() from the '@jeromyfu/google-play-scraper' library, then returns the results as a JSON string in the expected MCP content format.
    async ({ term, price, num, lang, country, fullDetail }) => {
      const results = await gplay.search({ term, price, num, lang, country, fullDetail });
      return { content: [{ type: "text", text: JSON.stringify(results) }] };
    }
  • Zod schema object defining the input parameters and their validation rules, descriptions, and defaults for the 'google-play-search' tool.
    {
      term: z.string().describe("Search term to query apps"),
      price: z.enum(["all", "free", "paid"]).default("all").describe("Filter by price: all, free, or paid (default: all)"),
      num: z.number().default(20).describe("Number of results to retrieve (default: 20, max: 250)"),
      lang: z.string().default("en").describe("Language code for result text (default: en)"), 
      country: z.string().default("us").describe("Country code to get results from (default: us)"),
      fullDetail: z.boolean().default(false).describe("Include full app details in results (default: false)")
    }, 
  • src/server.js:399-424 (registration)
    The complete server.tool() call that registers the 'google-play-search' tool, including its description string, input schema, and inline handler function.
    server.tool("google-play-search", 
      "Search for apps on Google Play. Returns a list of apps with:\n" +
      "- title: App name\n" +
      "- appId: Package name (e.g. 'com.company.app')\n" +
      "- url: Play Store URL\n" +
      "- icon: Icon image URL\n" +
      "- developer: Developer name\n" +
      "- developerId: Developer ID\n" +
      "- priceText: Price display text\n" +
      "- free: Boolean indicating if app is free\n" +
      "- summary: Short description\n" +
      "- scoreText: Rating display text\n" +
      "- score: Rating (0-5)",
      {
        term: z.string().describe("Search term to query apps"),
        price: z.enum(["all", "free", "paid"]).default("all").describe("Filter by price: all, free, or paid (default: all)"),
        num: z.number().default(20).describe("Number of results to retrieve (default: 20, max: 250)"),
        lang: z.string().default("en").describe("Language code for result text (default: en)"), 
        country: z.string().default("us").describe("Country code to get results from (default: us)"),
        fullDetail: z.boolean().default(false).describe("Include full app details in results (default: false)")
      }, 
      async ({ term, price, num, lang, country, fullDetail }) => {
        const results = await gplay.search({ term, price, num, lang, country, fullDetail });
        return { content: [{ type: "text", text: JSON.stringify(results) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format (list of apps with fields), which is helpful, but lacks critical behavioral details such as rate limits, authentication requirements, error handling, or pagination behavior for large result sets.

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 appropriately sized and front-loaded, starting with the core purpose. The bullet-point list of return fields is efficient, though it could be slightly more concise by grouping related fields (e.g., 'scoreText' and 'score').

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 moderate complexity (6 parameters, no output schema, no annotations), the description is partially complete. It explains the return format well but lacks behavioral context and usage guidelines. Without annotations or output schema, more detail on operational aspects would improve completeness.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no parameter-specific information beyond what the schema provides, such as examples or usage tips, meeting the baseline score for high schema coverage.

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 states the tool's purpose: 'Search for apps on Google Play.' It specifies the verb ('Search') and resource ('apps on Google Play'), and distinguishes it from siblings like 'google-play-details' or 'google-play-developer' by focusing on search functionality rather than detailed information retrieval.

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. It does not mention sibling tools like 'app-store-search' for Apple App Store searches or 'google-play-suggest' for autocomplete suggestions, leaving the agent without context for 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