Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_developer

List all App Store apps published by a specific Apple developer ID, with optional country and language filters, returning app details like title, price, ratings, and screenshots.

Instructions

Retrieve apps by developer ID. Lists the App Store apps published by one developer, by Apple developer (artist) id, for an optional storefront country and language. Each app carries its id, title, description, icon and screenshots, price and currency, genres, version and release notes, rating score and counts, size, supported devices and languages.

Input Schema

NameRequiredDescriptionDefault
langNoResult language tag
dev_idYesDeveloper artist ID
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 well: it enumerates the returned fields (price/currency, rating counts, version, release notes, supported devices/languages) so the agent knows the payload. 'Retrieve'/'Lists' implies a read-only operation, though read-only behavior is not stated outright, keeping it short of a 5.

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 with the core purpose front-loaded. The third sentence is a long field enumeration, which is justified because there is no output schema, but it is dense and could be trimmed slightly.

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 read-only, no-output-schema listing tool, the description supplies the return shape that the schema cannot, making the definition self-contained. Only the safety/read-only status is left implicit rather than declared.

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 dev_id, country, and lang are already documented in the schema. The description adds only the glosses 'artist id' and 'optional storefront country and language', which is marginal value beyond the schema. 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 (retrieve/list) plus resource (App Store apps by one developer) and the identifier type (Apple developer/artist id). An agent can distinguish this from siblings like appstore_app (single app), appstore_search, and googleplay_developer 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?

The opening sentence implies the usage context (you have a developer ID and want all their published apps), but there is no explicit when-to-use/when-not guidance and no alternatives named. Usage is inferable from the purpose but not spelled out.

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