Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

google-play-developer

Retrieve Google Play Store apps by developer to analyze portfolios, track competitor offerings, and research market presence with app details like ratings, pricing, and descriptions.

Instructions

Get apps by a developer on Google Play. Returns a list of apps with:

  • url: Play Store URL

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

  • title: App name

  • summary: Short app description

  • developer: Developer name

  • developerId: Developer ID

  • icon: Icon image URL

  • score: Rating (0-5)

  • scoreText: Rating display text

  • priceText: Price display text

  • free: Boolean indicating if app is free

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
devIdYesDeveloper name (e.g., 'DxCo Games')
langNoLanguage code for result text (default: en)en
countryNoCountry code to get results from (default: us)us
numNoNumber of results to retrieve (default: 60)
fullDetailNoInclude full app details in results (default: false), If fullDetail is true, includes all fields from app details endpoint.

Implementation Reference

  • The handler function that implements the core logic of the 'google-play-developer' tool. It calls the external gplay.developer() method with the input parameters and returns the results as a JSON string in the MCP content format.
    async ({ devId, lang, country, num, fullDetail }) => {
      const apps = await gplay.developer({ devId, lang, country, num, fullDetail });
      return { content: [{ type: "text", text: JSON.stringify(apps) }] };
    }
  • Zod schema defining the input parameters for the 'google-play-developer' tool: devId (required string), optional lang, country, num, fullDetail.
    {
      devId: z.string().describe("Developer name (e.g., 'DxCo Games')"),
      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)"),
      num: z.number().default(60).describe("Number of results to retrieve (default: 60)"),
      fullDetail: z.boolean().default(false).describe("Include full app details in results (default: false), If fullDetail is true, includes all fields from app details endpoint.")
    }, 
  • src/server.js:561-585 (registration)
    Registration of the 'google-play-developer' MCP tool via McpServer.tool() method, including tool name, description, input schema, and handler function.
    server.tool("google-play-developer", 
      "Get apps by a developer on Google Play. Returns a list of apps with:\n" +
      "- url: Play Store URL\n" +
      "- appId: Package name (e.g. 'com.company.app')\n" +
      "- title: App name\n" +
      "- summary: Short app description\n" +
      "- developer: Developer name\n" +
      "- developerId: Developer ID\n" +
      "- icon: Icon image URL\n" +
      "- score: Rating (0-5)\n" +
      "- scoreText: Rating display text\n" +
      "- priceText: Price display text\n" +
      "- free: Boolean indicating if app is free\n",
      {
        devId: z.string().describe("Developer name (e.g., 'DxCo Games')"),
        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)"),
        num: z.number().default(60).describe("Number of results to retrieve (default: 60)"),
        fullDetail: z.boolean().default(false).describe("Include full app details in results (default: false), If fullDetail is true, includes all fields from app details endpoint.")
      }, 
      async ({ devId, lang, country, num, fullDetail }) => {
        const apps = await gplay.developer({ devId, lang, country, num, fullDetail });
        return { content: [{ type: "text", text: JSON.stringify(apps) }] };
      }
    );
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. It describes the return format in detail but lacks behavioral context such as rate limits, authentication needs, error handling, or whether it's a read-only operation (implied by 'Get' but not explicit). This is a significant gap for a tool with no annotation coverage.

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?

The description is front-loaded with the core purpose, followed by a bulleted list of return fields that is well-structured and easy to parse. Every sentence earns its place, with no redundant or verbose language, making it highly efficient.

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 no annotations and no output schema, the description compensates by detailing the return format, which is helpful. However, it lacks context on behavioral aspects like rate limits or errors, and does not explain how parameters like 'fullDetail' affect the output beyond the schema. This leaves gaps for a tool with 5 parameters and no annotation support.

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 the schema already documents all 5 parameters thoroughly. The description does not add any parameter-specific information beyond what the schema provides, such as examples or usage tips. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 with specific verb ('Get apps') and resource ('by a developer on Google Play'), and distinguishes it from siblings like 'google-play-search' or 'google-play-list' by focusing on developer-specific retrieval. It explicitly mentions what it returns, making its function unambiguous.

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

Usage Guidelines3/5

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

The description implies usage when you need apps from a specific developer, but does not explicitly state when to use this tool versus alternatives like 'google-play-search' (for broader queries) or 'google-play-list' (for general listings). No exclusions or prerequisites are mentioned, leaving some ambiguity for the agent.

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