Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shop_app_suggestions

Generate Shop.app autocomplete suggestions for any query, returning up to 20 search terms or shop results with URLs and shop details.

Instructions

Suggest Shop.app searches. Returns Shop.app autocomplete suggestions for the required query. limit defaults to 10 and is capped at 20. Each suggestion is either a search query or a shop, with its text, type, URL and, for shops, the shop handle, name, rating and image.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum suggestions, defaults to 10 and supports up to 20
queryYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 burden of behavioral disclosure. It usefully describes the return shape, the default and capped limit, and that suggestions may be queries or shops, but it omits read-only confirmation, auth requirements, and any rate-limit or side-effect context.

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?

The description is front-loaded with the core action and then gives compact supporting detail. It is appropriately sized, though the opening 'Suggest Shop.app searches' and the following 'Returns Shop.app autocomplete suggestions' are slightly redundant.

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, the description correctly explains what each suggestion contains: `text`, `type`, URL, and shop-specific fields. For a low-complexity two-parameter tool this is nearly complete, with the main gap being usage context relative to sibling search and typeahead tools.

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 both `query` and `limit`. The description repeats the default and cap for `limit` and notes `query` is required, but adds no new syntax, format, or edge-case meaning beyond the schema.

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?

The description states a specific verb and resource: 'Suggest Shop.app searches' and 'Returns Shop.app autocomplete suggestions for the required `query`.' This is clear, but it never names or contrasts with sibling tools such as `shop_app_search` or `shop_app_shop_typeahead`, so an agent must infer the distinction from the name alone.

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?

The description provides no when-to-use guidance, no when-not-to-use guidance, and no alternatives. It only restates the purpose, leaving the agent to guess whether this is a pre-search typeahead helper or a standalone suggestion endpoint.

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