Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_privacy

Fetch App Store privacy disclosures for an app using its numeric track ID. Returns privacy policy URL, data categories, and purposes for the given country and language.

Instructions

Retrieve App Store privacy disclosures. Returns the privacy disclosures shown on an App Store page for one app, identified by its numeric track id (digits only; anything else returns 400). The response has privacy_policy_url, manage_privacy_choices_url and privacy_types, each with its data categories and purposes. country and lang are optional.

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.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the 400 on non-numeric ids, that the target is a single app, and enumerates the response payload (privacy_policy_url, manage_privacy_choices_url, privacy_types with data categories and purposes). It omits auth requirements and any rate-limit notes, so it falls short of fully transparent.

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 front-loaded sentences; purpose comes first, then input constraints, then return shape. Slight redundancy between the opening sentence and the following 'Returns the privacy disclosures...' clause, but nothing is wasted.

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?

There is no output schema, so the description does the work of sketching the return payload and input validation, which is nearly sufficient for a single-app read. Remaining gaps are minor: no mention of auth or request failure modes beyond the 400.

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. The description goes beyond the schema by adding the validation rule that anything other than digits returns 400 and by confirming country and lang are optional, giving the agent actionable input constraints.

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 and resource ('Retrieve App Store privacy disclosures') scoped to one app. No sibling covers privacy disclosures, and the description explicitly limits scope to a single app keyed by numeric track id, so an agent can separate it from appstore_app, appstore_ratings, or appstore_reviews without opening a 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 only implied: fetch this when you need the privacy disclosures shown on an app's store page for a given track id. There is no explicit when-to-use vs alternatives guidance, no stated prerequisites, and no exclusions – acceptable but with clear gaps.

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