Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

appstore_suggest

Retrieve App Store search suggestions for a partial term, with an optional two-letter storefront country code, to complete or refine app search queries.

Instructions

Retrieve App Store search suggestions. Returns App Store search suggestions for a partial search term given in the path, as a list of suggested term values. country is an optional two-letter storefront code.

Input Schema

NameRequiredDescriptionDefault
termYesPartial search term
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return shape (a list of suggested `term` values) and that `country` is optional, which is genuinely useful. However, it says nothing about read-only safety, rate limits, or empty-result behavior, leaving gaps for a zero-annotation 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?

Three tight sentences, front-loaded with the core action. Slight redundancy: sentence two repeats 'App Store search suggestions' from sentence one, and 'given in the path' is mildly confusing for an MCP parameter. Otherwise no waste.

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 simple 2-parameter read tool with no output schema and no annotations, the description covers purpose, input nature, and return shape adequately. Only the safety/behavioral profile and sibling differentiation are thin.

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% ('Partial search term', 'Two-letter storefront country code'), so the baseline is 3. The description largely restates the schema, adding only the word 'optional' for country, which the schema's required list already conveys. It does not add format examples or default-storefront behavior.

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) and resource (App Store search suggestions) and further pins down the semantics as typeahead-style suggestions ('partial search term', 'list of suggested `term` values'). This cleanly distinguishes it from the sibling appstore_search, which would take a full query.

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 phrase 'partial search term' implies the when-to-use context (autocomplete before a full search), but there is no explicit guidance contrasting it with appstore_search or any stated prerequisites/exclusions. Usage is inferable 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