Skip to main content
Glama
MiguelAlvRed

Store Scraper MCP

by MiguelAlvRed

search

Find mobile apps across App Store and Google Play Store by entering search terms, filtering by country and language, and specifying result quantity.

Instructions

Search for apps in the App Store

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term
countryNoTwo-letter country code (default: us)us
langNoLanguage code (default: en)en
numNoNumber of results (default: 50, max: 200)
pageNoPage number (default: 1)

Implementation Reference

  • Main handler function for the 'search' tool. Builds the iTunes search URL, fetches JSON data, parses it using parseSearch, and returns formatted results or error.
    async function handleSearch(args) {
      try {
        const {
          term,
          country = 'us',
          lang = 'en',
          num = 50,
          page = 1,
        } = args;
    
        if (!term) {
          throw new Error('term is required');
        }
    
        const url = buildSearchUrl({ term, country, lang, num, page });
        const data = await fetchJSON(url);
        const result = parseSearch(data);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ error: error.message }, null, 2),
            },
          ],
          isError: true,
        };
      }
  • Schema definition for the 'search' tool, including input parameters, defaults, and required fields, registered in ListToolsRequestSchema.
      name: 'search',
      description: 'Search for apps in the App Store',
      inputSchema: {
        type: 'object',
        properties: {
          term: {
            type: 'string',
            description: 'Search term',
          },
          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: 50, max: 200)',
            default: 50,
          },
          page: {
            type: 'number',
            description: 'Page number (default: 1)',
            default: 1,
          },
        },
        required: ['term'],
      },
    },
  • Tool dispatch registration in CallToolRequestSchema handler's switch statement, mapping 'search' tool name to handleSearch function.
    return await handleSearch(args);
  • Helper function to construct the iTunes Search API URL with pagination and limits, used by the search handler.
    export function buildSearchUrl(params) {
      const {
        term,
        country = 'us',
        lang = 'en',
        num = 50,
        page = 1,
        entity = 'software',
      } = params;
    
      const offset = (page - 1) * num;
      const queryParams = new URLSearchParams({
        term: term,
        country: country,
        lang: lang,
        limit: Math.min(num, 200).toString(),
        offset: offset.toString(),
        entity: entity,
      });
    
      return `${ITUNES_BASE}/search?${queryParams.toString()}`;
    }
  • Helper function to parse raw iTunes search API response into structured results, reusing parseApps, used by the search handler.
    export function parseSearch(data) {
      const apps = parseApps(data);
      
      return {
        results: apps,
        count: apps.length,
        total: data.resultCount || apps.length,
      };
    }
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. 'Search for apps' implies a read-only operation, but the description doesn't mention any behavioral traits like rate limits, authentication requirements, result format, or pagination behavior beyond what's in the schema. This is inadequate for a tool with 5 parameters.

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 states the core purpose without any wasted words. It's appropriately sized for a search tool and gets straight to the point with no unnecessary elaboration.

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?

For a search tool with 5 parameters and no output schema, the description is insufficient. It doesn't explain what kind of results to expect, how they're structured, or any limitations of the search functionality. With no annotations and no output schema, the description should provide more context about the tool's behavior and results.

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%, meaning all parameters are documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions, so it meets the baseline for high schema coverage without adding extra value.

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 ('Search for') and resource ('apps in the App Store'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'gp_search' or 'suggest', which appear to be related search functions, so it doesn't achieve full 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?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools that seem related to search functionality (gp_search, suggest, list), there's no indication of when this specific search tool is appropriate versus those other options.

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