Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_collections

Discover App Store editorial collections for a given Apple device. Returns collection links from Apple's browse page, which can be used to retrieve the collection's apps.

Instructions

Discover App Store editorial collections. Returns the room and EDS collection links embedded in Apple's browse page for one device. platform enum: iphone, ipad, mac, vision, watch, tv. Pass a returned id and the same platform to appstore_collection to retrieve the collection's apps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResult language tag
countryNoTwo-letter storefront country code
platformYesApple device catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 behavioral burden and does well: it discloses what is returned (room and EDS collection links embedded in Apple's browse page) and the scope (one device at a time). It doesn't cover auth or rate-limit behavior, but for a public read-only browse endpoint this is largely sufficient.

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 sentences, all purposeful and front-loaded with the core purpose before the workflow hint. The inline enum list slightly duplicates the schema, but it is compact and readable.

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?

With no output schema and no annotations, the description does enough by describing the returned content and the downstream handoff. The jargon terms 'room' and 'EDS' are left unexplained, which slightly reduces completeness for an agent trying to interpret the response.

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 schema already documents lang, country, and platform. The description's enumeration of platform values duplicates the schema enum and adds the 'one device' scoping notion but no syntax or format detail beyond that, so baseline 3 applies.

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 ('Discover') and resource ('App Store editorial collections'), and clearly separates itself from the sibling appstore_collection by describing the follow-up workflow. An agent can distinguish this discovery/browse step from the singular retrieval tool without opening either 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 explains the two-step workflow: pass a returned `id` and the same platform to `appstore_collection` to get the apps. It gives clear usage context, though it doesn't state when NOT to use this tool (e.g., if you already have an id, skip straight to appstore_collection).

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