Skip to main content
Glama
MiguelAlvRed

Store Scraper MCP

by MiguelAlvRed

app

Retrieve comprehensive app details from App Store and Google Play Store using ID or bundle identifier to analyze specifications and store listings.

Instructions

Get detailed information about an app by ID or bundleId

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoiTunes trackId of the app (e.g., 553834731)
appIdNoBundle ID of the app (e.g., com.midasplayer.apps.candycrushsaga)
countryNoTwo-letter country code (default: us)us

Implementation Reference

  • The main handler function that implements the core logic of the 'app' MCP tool. It builds the App Store lookup URL, fetches the data, parses it, and returns formatted JSON.
    /**
     * App tool - Get detailed information about an app
     */
    async function handleApp(args) {
      try {
        const { id, appId, country = 'us' } = args;
        
        if (!id && !appId) {
          throw new Error('Either id or appId must be provided');
        }
    
        const url = buildAppUrl({ id, appId, country });
        const data = await fetchJSON(url);
        const app = parseApp(data);
    
        if (!app) {
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify({ error: 'App not found' }, null, 2),
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(app, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ error: error.message }, null, 2),
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema definition for the 'app' tool, defining parameters like id, appId, and country.
      name: 'app',
      description: 'Get detailed information about an app by ID or bundleId',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'iTunes trackId of the app (e.g., 553834731)',
          },
          appId: {
            type: 'string',
            description: 'Bundle ID of the app (e.g., com.midasplayer.apps.candycrushsaga)',
          },
          country: {
            type: 'string',
            description: 'Two-letter country code (default: us)',
            default: 'us',
          },
        },
      },
    },
  • The switch case that registers and routes calls to the 'app' tool handler in the CallToolRequestSchema.
    case 'app':
      return await handleApp(args);
  • The parseApp helper function that normalizes raw iTunes API response into a structured app object used by the handler.
    export function parseApp(data) {
      if (!data || !data.results || data.results.length === 0) {
        return null;
      }
    
      const app = data.results[0];
    
      return {
        id: app.trackId || null,
        appId: app.bundleId || null,
        title: app.trackName || null,
        url: app.trackViewUrl || null,
        description: app.description || null,
        releaseNotes: app.releaseNotes || null,
        version: app.version || null,
        releaseDate: app.releaseDate || null,
        currentVersionReleaseDate: app.currentVersionReleaseDate || null,
        price: app.price || 0,
        currency: app.currency || null,
        free: app.price === 0,
        developer: {
          id: app.artistId || null,
          name: app.artistName || null,
          url: app.artistViewUrl || null,
        },
        category: {
          id: app.primaryGenreId || null,
          name: app.primaryGenreName || null,
          genres: app.genres || [],
        },
        rating: {
          average: app.averageUserRating || null,
          count: app.userRatingCount || 0,
        },
        contentAdvisoryRating: app.contentAdvisoryRating || null,
        screenshotUrls: app.screenshotUrls || [],
        ipadScreenshotUrls: app.ipadScreenshotUrls || [],
        appletvScreenshotUrls: app.appletvScreenshotUrls || [],
        artwork: {
          icon: app.artworkUrl512 || app.artworkUrl100 || app.artworkUrl60 || null,
          icon60: app.artworkUrl60 || null,
          icon100: app.artworkUrl100 || null,
          icon512: app.artworkUrl512 || null,
        },
        supportedDevices: app.supportedDevices || [],
        minimumOsVersion: app.minimumOsVersion || null,
        languageCodesISO2A: app.languageCodesISO2A || [],
        fileSizeBytes: app.fileSizeBytes || null,
        sellerName: app.sellerName || null,
        formattedPrice: app.formattedPrice || null,
        isGameCenterEnabled: app.isGameCenterEnabled || false,
        features: app.features || [],
        advisories: app.advisories || [],
        kind: app.kind || null,
        averageUserRatingForCurrentVersion: app.averageUserRatingForCurrentVersion || null,
        userRatingCountForCurrentVersion: app.userRatingCountForCurrentVersion || 0,
      };
    }
  • The buildAppUrl helper that constructs the correct iTunes lookup URL based on id or appId parameters.
    export function buildAppUrl(params) {
      const { id, appId, country = 'us' } = params;
      
      if (id) {
        return `${ITUNES_BASE}/lookup?id=${id}&country=${country}`;
      }
      
      if (appId) {
        // First lookup by bundleId to get trackId
        return `${ITUNES_BASE}/lookup?bundleId=${appId}&country=${country}`;
      }
      
      throw new Error('Either id or appId must be provided');
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it implies a read-only operation ('Get detailed information'), it doesn't address important behavioral aspects like what 'detailed information' includes, whether there are rate limits, authentication requirements, error conditions, or how the country parameter affects results. This leaves significant gaps for an agent.

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 extremely concise (8 words) and front-loaded with the core purpose. Every word earns its place, with no redundant information or unnecessary elaboration. This is model efficiency in technical documentation.

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 tool's apparent simplicity (lookup by identifier), no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'detailed information' includes, how results are structured, what happens when multiple identifiers are provided, or how this differs from similar tools in the sibling list. The agent would need to guess about the tool's behavior and output.

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 fully documents all three parameters. The description adds no additional parameter semantics beyond what's in the schema - it mentions 'ID or bundleId' but doesn't explain their relationship or exclusivity. This meets the baseline for 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 tool's purpose with a specific verb ('Get detailed information') and resource ('about an app'), making it immediately understandable. However, it doesn't differentiate this tool from potential sibling tools like 'developer', 'gp_app', or 'search' that might also retrieve app information, which prevents a perfect score.

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 'search', 'gp_app', or 'developer' from the sibling list. It mentions two identifier options (ID or bundleId) but doesn't explain when one might be preferred over the other or what happens if both are provided.

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