Crawlora MCP

appstore_search

Read-only

Search Apple's App Store catalog by query and storefront. Use appstore_suggest for typeahead, appstore_developer for one developer's catalog, appstore_app for a known track id, or datasets_apps_search for cross-store iOS and Google Play records.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "Term": "<Term>"
    },
    "name": "appstore_search"
  }
}

Input Schema

Name	Required	Description
`Num`	No	Number of results to return. Default 50.
`Lang`	No	Result language tag, e.g. en-US.
`Page`	No	Result page number, starting at 1. Default 1.
`Term`	Yes	App Store search query. Required.
`Country`	No	ISO-2 storefront country code, e.g. us. Default us.
`IDsOnly`	No	Return only app IDs instead of full app objects when true. Default false.
`Platform`	No	App Store catalog to search. Default phone. Allowed values: phone, pad, mac. pad and mac search Apple's iPad-specific and Mac App Store catalogs; most universal apps already appear under phone.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds little beyond that, saying nothing about pagination behavior, rate limits, or auth. Adequate against a lower annotation-backed bar, but not rich.

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?

Two sentences: purpose first, then a compressed set of alternative routes. Every clause earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Purpose and sibling routing are fully covered; nothing needed to call this correctly is missing.

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 all seven parameters. The phrase 'by query and storefront' maps to Term and Country but adds no syntax or format detail beyond the schema. Baseline 3 is correct.

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 (Search), resource (Apple's App Store catalog), and scope (by query and storefront). It explicitly names and contrasts four sibling tools, so an agent can distinguish it 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 Guidelines5/5

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

Names the alternatives and the exact condition that selects each: appstore_suggest for typeahead, appstore_developer for a single developer's catalog, appstore_app for a known track id, and datasets_apps_search for cross-store data. Routing is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?