Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_search

Search the App Store by term and platform to retrieve app results or only app IDs. Filter by country, language, page, and count for structured app data.

Instructions

Search the App Store. Returns App Store search results for a term. Set ids_only=true to return only app IDs. platform enum: phone, pad, mac.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoNumber of apps per page
langNoResult language tag
pageNoSearch page number (1-based)
termYesSearch term
countryNoTwo-letter storefront country code
ids_onlyNoReturn only app IDs
platformNoApp Store catalog to search: phone, pad, mac

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / platform / enum
      Added value: +[
+  "phone",
+  "pad",
+  "mac"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "App Store catalog to search: phone, pad, mac",
+  "type": "string"
+}
  3. First observedv1.0.0

TDQS

C2.9/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 mentions the ids_only mode and platform values, but these largely restate schema definitions. It does not disclose the response shape, default pagination behavior, result ordering, storefront defaults, rate limits, or failure modes, leaving the agent with an unclear model of what a call returns.

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 short sentences with the purpose front-loaded. It is efficient and readable, though the final sentence about the platform enum is redundant with the schema's enum definition and does not fully earn its place.

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

Completeness2/5

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

The tool has no output schema and no annotations, yet the description never explains what App Store search results contain (app metadata fields, ratings, prices), how pagination defaults work, or what values country and lang expect beyond the schema's terse hints. For a 7-parameter search endpoint, an agent is left guessing at invocation expectations and response interpretation.

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 of 3 applies. The description repeats ids_only and platform without adding meaning beyond the schema's descriptions (e.g., 'Return only app IDs', 'App Store catalog to search'), and it adds nothing about country, lang, page, or num that the schema doesn't already convey.

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?

States a specific verb and resource: searching the App Store for a term. The purpose is unmistakable, but the description does not differentiate from semantically close siblings like appstore_suggest, appstore_app, or appstore_list, so an agent must infer the boundary between search and lookup/suggestion tools.

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 guidance is given on when to use this tool versus alternatives such as appstore_suggest, appstore_app, appstore_list, or appstore_ratings. The description explains modifier behavior (ids_only, platform) but never addresses selection logic among the App Store sibling tools.

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