Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

app-store-version-history

Retrieve version history for App Store apps to track updates, review release notes, and analyze development timelines.

Instructions

Get version history for an App Store app. Returns an array of versions with:

  • versionDisplay: Version number string

  • releaseNotes: Update description

  • releaseDate: Release date (YYYY-MM-DD)

  • releaseTimestamp: Release date and time (ISO string)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric App ID (e.g., 444934666)

Implementation Reference

  • Handler function for 'app-store-version-history' tool. Takes app ID, calls store.versionHistory() from the app-store-scraper library, and returns the JSON-stringified history as text content.
    async ({ id }) => {
      const history = await store.versionHistory({ id });
      return { content: [{ type: "text", text: JSON.stringify(history) }] };
    }
  • Input schema for the tool, defining a required 'id' parameter as a number representing the App Store app ID.
    {
      id: z.number().describe("Numeric App ID (e.g., 444934666)")
    }, 
  • src/server.js:234-247 (registration)
    Registration of the 'app-store-version-history' tool using McpServer.tool(), including description, input schema with Zod, and inline async handler.
    server.tool("app-store-version-history", 
      "Get version history for an App Store app. Returns an array of versions with:\n" +
      "- versionDisplay: Version number string\n" +
      "- releaseNotes: Update description\n" +
      "- releaseDate: Release date (YYYY-MM-DD)\n" +
      "- releaseTimestamp: Release date and time (ISO string)",
      {
        id: z.number().describe("Numeric App ID (e.g., 444934666)")
      }, 
      async ({ id }) => {
        const history = await store.versionHistory({ id });
        return { content: [{ type: "text", text: JSON.stringify(history) }] };
      }
    );
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. It describes the return format (array of versions with specific fields) but lacks critical behavioral details such as whether this is a read-only operation, potential rate limits, authentication requirements, or error handling for invalid IDs. The description is insufficient for a tool with no annotation coverage.

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 front-loaded with the core purpose ('Get version history for an App Store app') and efficiently lists the return fields in a bulleted format. Every sentence earns its place by providing essential information without redundancy or fluff, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description is partially complete. It explains the return format clearly, which compensates for the lack of output schema, but fails to address behavioral aspects like safety or constraints. It is adequate for basic use but has gaps in guidance and transparency.

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, with the 'id' parameter documented as 'Numeric App ID (e.g., 444934666)'. The description adds no additional parameter information beyond what the schema provides, such as format constraints or examples. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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') and resource ('version history for an App Store app'), distinguishing it from siblings like app-store-details or app-store-reviews by focusing on historical version data rather than current details or user feedback.

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. It does not mention prerequisites, such as needing an App ID, or differentiate from similar tools like app-store-details, which might overlap in functionality. Usage is implied but not explicitly stated.

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/JiantaoFu/AppInsightMCP'

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