Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

duckduckgo_search

Search DuckDuckGo web results and retrieve decoded destination URLs with titles, descriptions, hostnames, and pagination; supports region, time range, and safe search filters.

Instructions

Search DuckDuckGo web results. Returns DuckDuckGo web search results for a query string: title, destination URL, description, and hostname, plus page-based pagination. DuckDuckGo wraps every result link in its own click-tracking redirect; this endpoint always returns the decoded destination URL, never the raw redirect link.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
pageNo1-based page number, defaults to 1
regionNoDuckDuckGo region/locale code, e.g. us-en, uk-en, wt-wt (worldwide, the default)
time_rangeNoRestrict results to a recency window
safe_searchNoSafe search level, defaults to DuckDuckGo's own moderate setting when omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / safe_search / enum
      Added value: +[
+  "strict",
+  "moderate",
+  "off"
+]
    • addedInput schema / properties / time_range / enum
      Added value: +[
+  "d",
+  "w",
+  "m",
+  "y"
+]
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does meaningful work: it enumerates the return fields (title, URL, description, hostname), notes page-based pagination, and explains the click-tracking redirect quirk and the guarantee that decoded destination URLs are always returned. It omits rate limiting, auth and error behavior, but the redirect disclosure is exactly the kind of hidden behavior an agent cannot infer from the schema.

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 sentences, front-loaded with the purpose followed by return shape and the redirect caveat. Efficient, though the redirect sentence is fairly long; nothing is wasted.

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?

Because there is no output schema, the description usefully documents the return fields itself. Combined with 100% parameter coverage and a predictable read-only search semantics, the only gap is the absence of any note on rate limits, errors, or result-count behavior.

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 every parameter (q, page, region, time_range, safe_search) is already documented at the schema level, giving a baseline of 3. The description adds only 'page-based pagination' and no extra syntax or semantics for region, time_range or safe_search beyond what the schema provides.

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 ('Search DuckDuckGo web results') and the 'web results' scope implicitly separates it from the vertical siblings duckduckgo_image, duckduckgo_news and duckduckgo_shopping. It does not, however, explicitly name an alternative the way the highest-scoring examples do.

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?

There is no when-to-use or when-not-to-use guidance, and no routing to alternatives such as duckduckgo_news, brave_search, web_search or bing_search, despite the huge sibling set of competing search tools. Usage is only implied by the tool name and scope.

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