Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_app

Fetch full App Store metadata for an iPhone, iPad, or Mac app using its numeric track ID or bundle ID, with optional country, language, ratings, and platform details.

Instructions

Retrieve full App Store app details. Returns app metadata from the App Store. Provide either id (numeric track ID) or app_id (bundle ID). id/app_id can identify an iPhone, iPad, or Mac App Store listing.

Input Schema

NameRequiredDescriptionDefault
idNoApp Store numeric track ID (digits only)
langNoResult language tag
app_idNoApp Store bundle ID
countryNoTwo-letter storefront country code
ratingsNoInclude ratings histogram
platformsNoInclude the full device-platform compatibility list (adds one extra upstream fetch)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / platforms
      Added value: +{
+  "description": "Include the full device-platform compatibility list (adds one extra upstream fetch)",
+  "type": "boolean"
+}
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the return is App Store metadata and that id/app_id can target iPhone, iPad, or Mac listings, but omits auth/permission needs, error behavior when neither identifier is given despite required: [], and response shape. Moderate disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short, front-loaded sentences with the purpose stated first and identifier guidance second. Slight redundancy between 'full App Store app details' and 'Returns app metadata from the App Store', but no padding.

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?

With no annotations and no output schema, the description must carry more weight. It covers the identifier requirement and platform scope, but 'app metadata' is never concretized (no mention of pricing, screenshots, developer, version, etc.), so an agent cannot anticipate the return payload.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the critical either/or rule (`id` or `app_id`), which the schema does not express since required is empty. It also notes these identifiers span iPhone/iPad/Mac listings, adding meaning beyond the per-field descriptions.

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?

States a specific verb (Retrieve) and resource (full App Store app details), and clarifies it returns metadata. This distinguishes it from search/suggest siblings, though it never names which sibling to use instead. Clear purpose, but no explicit sibling differentiation.

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?

The description implies it is a lookup-by-identifier tool and states you must provide either `id` or `app_id`, but never says when to use this versus appstore_search or appstore_list. Usage is inferred rather than contrasted with alternatives.

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