Skip to main content
Glama
MiguelAlvRed

Store Scraper MCP

by MiguelAlvRed

versionHistory

Retrieve app version history and release notes from app stores using the app's unique identifier.

Instructions

Get app version history with release notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesiTunes trackId of the app
countryNoTwo-letter country code (default: us)us

Implementation Reference

  • Main handler function that fetches the version history URL using buildVersionHistoryUrl, parses the data with parseVersionHistory, and returns the formatted JSON response.
    /**
     * VersionHistory tool - Get app version history
     */
    async function handleVersionHistory(args) {
      try {
        const { id, country = 'us' } = args;
    
        if (!id) {
          throw new Error('id is required');
        }
    
        const url = buildVersionHistoryUrl({ id, country });
        const data = await fetchJSON(url);
        const history = parseVersionHistory(data);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                id,
                versionHistory: history,
                count: history.length,
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ error: error.message }, null, 2),
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema definition for the versionHistory tool, specifying required 'id' parameter and optional 'country'.
    {
      name: 'versionHistory',
      description: 'Get app version history with release notes',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'iTunes trackId of the app',
          },
          country: {
            type: 'string',
            description: 'Two-letter country code (default: us)',
            default: 'us',
          },
        },
        required: ['id'],
      },
    },
  • Dispatch registration in the CallToolRequestSchema handler switch statement that routes calls to handleVersionHistory.
    case 'versionHistory':
      return await handleVersionHistory(args);
  • Helper function to parse raw version history data from the API response into a normalized array of version objects.
    export function parseVersionHistory(data) {
      if (!data || !Array.isArray(data)) {
        return [];
      }
    
      return data.map(version => ({
        versionDisplay: version.versionDisplay || version.version || null,
        releaseNotes: version.releaseNotes || null,
        releaseDate: version.releaseDate || null,
        releaseTimestamp: version.releaseTimestamp || null,
      }));
    }
  • Helper function to construct the iTunes App Store version history API URL.
    export function buildVersionHistoryUrl(params) {
      const { id, country = 'us' } = params;
      
      if (!id) {
        throw new Error('id must be provided for version history');
      }
      
      return `${ITUNES_BASE}/us/app-version-history/${id}.json`;
    }
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 traits like rate limits, error handling, authentication needs, or response format. For a read operation with no annotations, this is a significant gap in transparency.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of retrieving version history and the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects, response structure, or usage context, which are crucial for an agent to invoke this tool effectively in a server with many similar tools.

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%, so the schema already documents both parameters (id and country) adequately. The description doesn't add any meaning beyond this, such as explaining what 'iTunes trackId' entails or how the country code affects results, but the baseline is 3 when the schema does the heavy lifting.

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 the resource 'app version history with release notes', making the purpose evident. However, it doesn't distinguish this tool from its siblings (like 'app' or 'list'), which might also retrieve app-related information, so it doesn't achieve full 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 many sibling tools (e.g., 'app', 'list', 'reviews'), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on the name alone.

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