Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shop_app_search

Search Shop.app product listings by query and optionally filter for sale or in-stock items, with result limits up to 50.

Instructions

Search Shop.app products. Searches Shop.app product results. Limit defaults to 20 and accepts values up to 50.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum products, defaults to 20 and supports up to 50
queryYesSearch query
on_saleNoRequest sale products
in_stockNoRequest in-stock products
deep_searchNoAccepted for compatibility; Shop.app no longer offers a separate deep search mode, so results are unchanged

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.12
    • changedInput schema / properties / deep_search / description
      Previous value: -"Enable Shop.app deep search mode"New value: +"Accepted for compatibility; Shop.app no longer offers a separate deep search mode, so results are unchanged"
  2. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it adds nothing beyond the schema: it restates the limit default/range already in the schema and says nothing about pagination, result ordering, or return shape. It also omits the notable fact (present only in the schema) that deep_search is a no-op kept for compatibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, but the first two are redundant ("Search Shop.app products" / "Searches Shop.app product results"), so roughly a third of the text is wasted. The useful limit note is present but is duplicative of the schema.

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?

With five parameters, no annotations, and no output schema, the description should do more to explain what a result looks like and how the boolean filters affect results. It leaves the agent without enough to predict the response or the effect of the flags.

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 five parameters, including the deep_search compatibility caveat. The description repeats the limit default/max but adds no meaning for query, on_sale, in_stock, or how filters combine. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search Shop.app products" gives a clear verb+resource, but the second sentence ("Searches Shop.app product results") merely restates the first. There is no differentiation from the many sibling search tools (shop_app_product, shop_app_shop_products, costco_search, walmart_search, etc.), so the agent cannot distinguish scope from the text 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?

No when-to-use guidance, no exclusions, and no named alternative. For a product search sitting alongside shop_app_product, shop_app_shop_products, and shop_app_suggestions, the description never states when this tool is the right entry point versus those siblings.

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