Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_collection

Fetch all apps listed in a specific App Store collection by providing platform and collection ID, returning structured JSON app items.

Instructions

Retrieve apps in one App Store collection. Returns app items embedded in an Apple room or EDS collection page. Discover IDs with appstore_collections. platform enum: iphone, ipad, mac, vision, watch, tv. collection_id must be a numeric room ID or eds.UUID ID returned by the discovery endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResult language tag
countryNoTwo-letter storefront country code
platformYesApple device catalog
collection_idYesRoom ID or EDS UUID collection ID from appstore_collections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior3/5

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

No annotations, so the description carries full burden. It discloses return content ('app items embedded in an Apple room or EDS collection page'), which is genuinely useful behavioral context, but stays silent on pagination, result limits, and auth/read-only status expected of a retrieval tool.

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?

Front-loads purpose, then ID discovery, then parameter formats in three compact sentences. Efficient with no filler, though the trailing parameter notes read as a list rather than integrated guidance.

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 two-required-param read tool with a fully documented schema and no output schema, the description covers what is returned, how to obtain the collection_id, and platform options. Only pagination/limit behavior is unaddressed.

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 description coverage is 100%, so the baseline is 3. The description restates the platform enum and the collection_id format (numeric room ID or eds.UUID), which largely duplicates what the schema already documents rather than adding new syntax or 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 apps in one App Store collection') and distinguishes itself from the sibling appstore_collections by naming it as the ID-discovery step. An agent can separate this from appstore_search 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 Guidelines4/5

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

Explicitly routes the agent: 'Discover IDs with appstore_collections' and requires collection_id to come from that discovery endpoint. This is clear context for when to reach for the sibling first, though it does not state exclusions against search/list 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