Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

duckduckgo_shopping

Search DuckDuckGo shopping listings by query and region to retrieve product titles, brands, merchants, prices, ratings, review counts, and total page count.

Instructions

Search DuckDuckGo shopping results. Returns DuckDuckGo shopping results for a query string: title, brand, merchant, description, price, rating, and review count, plus total page count. DuckDuckGo's shopping vertical is ad-funded, syndicated product listings, not organic content; every product link is wrapped in an ad-click-tracking redirect with no clean destination to unwrap, so no destination URL is returned. DuckDuckGo's own pagination token for this vertical is an opaque per-response blob rather than a plain page offset, so only the first page is supported.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
regionNoDuckDuckGo market code, e.g. us-en, uk-en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discharges it well: it discloses that listings are ad-funded syndication, that every link is an ad-click-tracking redirect with no unwrappable destination, and that the pagination token is an opaque blob so only page one is available. These are exactly the operational facts an agent needs to avoid misusing results.

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?

Purpose is front-loaded in the first sentence, followed by return fields and then the two caveats. It is somewhat dense and the pagination explanation is wordy, but each sentence conveys a distinct, useful fact.

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?

With no output schema and no annotations, the description is complete for the task: it lists the returned fields, states the two hard limitations, and explains why (ad-funded redirects, opaque token). Nothing an agent needs to call it 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 coverage is 100%, so both `q` and `region` are already documented in the schema. The description alludes to the query string but adds no semantics for `region` or query formatting, so baseline 3 applies.

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 and resource ("Search DuckDuckGo shopping results") and then enumerates exactly what comes back (title, brand, merchant, price, rating, review count, page count). The scoping to DuckDuckGo's ad-funded shopping vertical makes it readily distinguishable from generic search or other retailer tools.

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?

Usage is implied by the vertical description and the stated constraints (first page only, no destination URL), which tell an agent when the result set is usable. However, no alternative tool is named or contrasted (e.g., duckduckgo_search, yahoo_shopping_*, amazon_product), so the routing between siblings is left to inference.

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