Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_privacy

Retrieve App Store privacy cards, including data categories and purposes, for an app by numeric track ID, with optional language and country filters.

Instructions

Retrieve App Store privacy disclosures. Returns the app privacy cards shown on the App Store page, including data categories and purposes.

Input Schema

TableJSON 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

B3.2/5.0
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 simply states it retrieves and returns privacy cards, but does not disclose rate limits, authentication needs, error handling, or data freshness. The behavior is implied as a read-only retrieval, but more detail would be beneficial.

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 extremely concise, consisting of two sentences that convey the purpose and return value without any extraneous information. Every word earns its place.

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?

Given the tool's simplicity and the fact that the input schema covers all parameters, the description is mostly complete. It clearly explains what the tool returns. However, it could mention that the required parameter 'id' is an App Store track ID, which is only in the schema, not the description. Minor gap.

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 description adds no additional meaning beyond the input schema, which already has 100% coverage with descriptions for all three parameters. The schema provides the parameter definitions, so the description does not need to add more, but it also does not enhance understanding. Baseline 3 is appropriate.

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?

The description clearly states the verb 'Retrieve' and the resource 'App Store privacy disclosures', and specifies that it returns privacy cards with data categories and purposes. However, it does not explicitly distinguish this tool from sibling tools like appstore_app, which might also be used to get app details.

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?

No usage guidelines are provided. The description does not mention when to use this tool instead of alternatives, nor does it indicate any prerequisites or constraints. Agents must infer that it's for privacy data only.

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