Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

appstore_version_history

Fetch an App Store app's version history by numeric track ID, with optional country and language, to see version numbers, release dates, and release notes.

Instructions

Retrieve App Store version history. Returns an App Store app's version history, as shown under "What's New", by numeric track id, for an optional storefront country and language. Each entry has the version number, release date and timestamp, and release notes. A non-numeric id returns 400.

Input Schema

NameRequiredDescriptionDefault
idYesApp Store numeric track ID (digits only)
langNoResult language tag
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

A4/5.0
Behavior4/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. It does disclose meaningful behavior beyond the fields: the exact contents of each entry (version number, release date and timestamp, release notes) and an error condition (non-numeric id returns 400). Read-only nature is implied but not explicitly stated, keeping it shy of a 5.

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?

Three tight sentences, front-loaded with the core purpose, then result content, then the error edge case. No filler and every sentence adds information.

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

Completeness4/5

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

For a simple read tool with no annotations and no output schema, the description covers return contents and an error behavior, which is enough to call it correctly. Minor gaps (no pagination or read-only statement) keep it from 5, but the essential context is present.

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 coverage is 100%, so id ('numeric track ID, digits only'), lang, and country are already documented in the schema. The description reinforces that id must be numeric and that country/language are optional and storefront-scoped, but adds no syntax or format detail beyond the schema baseline.

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?

States a specific verb (Retrieve) and resource (App Store version history), then clarifies it is the 'What's New' release history keyed by track id. This is clearly distinguishable from siblings like appstore_reviews, appstore_ratings, or appstore_app without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the resource (fetch an app's version/changelog history) but the description never says when to prefer this over appstore_reviews/appstore_app or what prerequisites exist. No exclusions or alternative routing are provided, so guidance is only inferable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools