Skip to main content
Glama
MiguelAlvRed

Store Scraper MCP

by MiguelAlvRed

gp_list

Retrieve Google Play Store app rankings for top free, paid, grossing, and trending apps by category and country.

Instructions

[Google Play] Get app rankings (top free, paid, grossing)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionNoCollection type: topselling_free, topselling_paid, topgrossing, movers_shakerstopselling_free
categoryNoCategory ID (default: APPLICATION)APPLICATION
countryNoTwo-letter country code (default: us)us
langNoLanguage code (default: en)en
numNoNumber of results (default: 60)

Implementation Reference

  • The main handler function for the 'gp_list' tool. It extracts parameters from args, constructs the Google Play list URL, fetches the HTML, parses it using parseGPList, and returns the list of apps in JSON format.
    async function handleGPList(args) {
      try {
        const {
          collection = 'topselling_free',
          category = 'APPLICATION',
          country = 'us',
          lang = 'en',
          num = 60,
        } = args;
    
        const url = buildGPListUrl({ collection, category, country, lang, num });
        const html = await fetchText(url);
        const apps = parseGPList(html);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                collection,
                category,
                country,
                results: 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 for the 'gp_list' tool, defining parameters such as collection, category, country, lang, and num with their types, descriptions, defaults, and enums.
    {
      name: 'gp_list',
      description: '[Google Play] Get app rankings (top free, paid, grossing)',
      inputSchema: {
        type: 'object',
        properties: {
          collection: {
            type: 'string',
            description: 'Collection type: topselling_free, topselling_paid, topgrossing, movers_shakers',
            default: 'topselling_free',
            enum: ['topselling_free', 'topselling_paid', 'topgrossing', 'movers_shakers'],
          },
          category: {
            type: 'string',
            description: 'Category ID (default: APPLICATION)',
            default: 'APPLICATION',
          },
          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,
          },
        },
      },
    },
  • Registration in the tool dispatch switch statement: routes calls to 'gp_list' to the handleGPList function.
    case 'gp_list':
      return await handleGPList(args);
  • Helper parser function parseList (imported as parseGPList) that extracts app data from Google Play list page HTML by reusing the search parser.
    export function parseList(html) {
      // List pages use similar structure to search results
      return parseSearch(html);
    }
  • Helper function buildListUrl (imported as buildGPListUrl) that constructs the Google Play list/ranking URL based on parameters.
    export function buildListUrl(params) {
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 states what the tool does but lacks details on rate limits, authentication requirements, error handling, or output format (e.g., pagination, data structure). For a tool with no annotations, this leaves significant gaps in understanding its operational behavior.

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 concise and front-loaded with the core purpose in a single, efficient sentence. There's no wasted text, and it immediately conveys the tool's function without unnecessary elaboration, making it easy to parse.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the rankings output looks like (e.g., list format, fields included), potential limitations, or error conditions. For a tool with 5 parameters and no structured output documentation, more contextual information is needed to fully understand its use.

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 all 5 parameters with defaults and enums. The description adds minimal value beyond the schema by implying the tool retrieves rankings based on these parameters, but doesn't provide additional context like parameter interactions or usage examples. Baseline 3 is appropriate given high schema coverage.

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 action ('Get app rankings') and specifies the resource domain ('Google Play'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'gp_search', 'gp_reviews', or 'list', which might also retrieve Google Play data but for different purposes.

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 like 'gp_search' (for searching apps) or 'gp_reviews' (for reviews). It mentions ranking types (top free, paid, grossing) but doesn't clarify scenarios where one type is preferred over another or when this tool is appropriate compared to siblings.

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