Fetch App Store version history by providing an app's numeric track ID. Get release notes and update entries from the "What's New" section as clean JSON.
Retrieve App Store version history. Returns the version history entries shown in the App Store "What's New" section.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | App Store numeric track ID (digits only) | |
| lang | No | Result language tag | |
| country | No | Two-letter storefront country code |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations. Description mentions return content but lacks details on behavior like pagination, limits, or error cases. Adequate for a read tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with purpose, no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Describes what is returned (version history entries). No output schema, but tool is simple. Could mention pagination or limits, but overall adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with descriptions. Description adds no additional parameter info, baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states action 'Retrieve App Store version history' and specifies it returns the entries shown in the 'What's New' section. Distinct from sibling tools like appstore_app.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs alternatives. Implied usage for version history, but no when-not-to-use or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.