Skip to main content
Glama
MiguelAlvRed

Store Scraper MCP

by MiguelAlvRed

gp_developer

Retrieve all applications published by a specific developer on Google Play Store using their developer ID. Supports country, language, and result count parameters for targeted data collection.

Instructions

[Google Play] Get all apps by a developer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
devIdYesGoogle Play developer ID
countryNoTwo-letter country code (default: us)us
langNoLanguage code (default: en)en
numNoNumber of results (default: 60)

Implementation Reference

  • The handler function that implements the core logic for the 'gp_developer' tool. It constructs the developer URL, fetches the HTML, parses the app list using parseGPList, and returns structured JSON data or an error.
    async function handleGPDeveloper(args) {
      try {
        const { devId, country = 'us', lang = 'en', num = 60 } = args;
    
        if (!devId) {
          throw new Error('devId is required');
        }
    
        const url = buildGPDeveloperUrl({ devId, country, lang, num });
        const html = await fetchText(url);
        const apps = parseGPList(html); // Uses same parser as list
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                developerId: devId,
                apps,
                count: apps.length,
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ error: error.message }, null, 2),
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema definition for the 'gp_developer' tool, specifying parameters like devId (required), country, lang, and num.
    inputSchema: {
      type: 'object',
      properties: {
        devId: {
          type: 'string',
          description: 'Google Play developer ID',
        },
        country: {
          type: 'string',
          description: 'Two-letter country code (default: us)',
          default: 'us',
        },
        lang: {
          type: 'string',
          description: 'Language code (default: en)',
          default: 'en',
        },
        num: {
          type: 'number',
          description: 'Number of results (default: 60)',
          default: 60,
        },
      },
      required: ['devId'],
  • The tool registration in the ListTools handler, defining name, description, and input schema for 'gp_developer'.
      name: 'gp_developer',
      description: '[Google Play] Get all apps by a developer',
      inputSchema: {
        type: 'object',
        properties: {
          devId: {
            type: 'string',
            description: 'Google Play developer ID',
          },
          country: {
            type: 'string',
            description: 'Two-letter country code (default: us)',
            default: 'us',
          },
          lang: {
            type: 'string',
            description: 'Language code (default: en)',
            default: 'en',
          },
          num: {
            type: 'number',
            description: 'Number of results (default: 60)',
            default: 60,
          },
        },
        required: ['devId'],
      },
    },
  • The dispatch case in the CallToolRequestSchema handler that routes calls to the gp_developer handler function.
    case 'gp_developer':
      return await handleGPDeveloper(args);
  • Import alias for the URL builder function used in the gp_developer handler, from './endpoints/googlePlay.js'.
    buildDeveloperUrl as buildGPDeveloperUrl,
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get all apps' but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior, or what the output format looks like. For a tool with no annotations and no output schema, this leaves significant gaps in understanding how it behaves.

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 a single, efficient sentence that front-loads the core purpose. Every word earns its place: '[Google Play]' provides context, 'Get all apps by a developer' is the action, and there's no redundant information. It's appropriately sized for this tool's complexity.

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

Completeness2/5

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

Given no annotations, no output schema, and 4 parameters (with 1 required), the description is incomplete. It doesn't explain what the tool returns (e.g., list of app objects with basic details), behavioral constraints, or error conditions. For a data retrieval tool in a sibling-rich environment, this leaves the agent with insufficient context to use it effectively.

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 fully documents all 4 parameters (devId, country, lang, num) with descriptions and defaults. The description adds no additional parameter semantics beyond implying the tool uses these to fetch apps. Baseline 3 is appropriate since the schema does the heavy lifting, but the description doesn't compensate with extra context like parameter interactions.

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 verb ('Get') and resource ('all apps by a developer') with the context '[Google Play]'. It distinguishes from siblings like 'gp_app' (single app) and 'developer' (generic developer info), but doesn't explicitly differentiate from 'gp_search' which could also find apps by developer. The purpose is specific but could be more precise about sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'gp_search', 'developer', and 'gp_list', the description doesn't indicate this is the primary tool for retrieving all apps from a specific developer ID. There's no mention of prerequisites, limitations, or comparison to other tools.

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/MiguelAlvRed/mobile-store-scraper-mcp'

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