Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

duckduckgo_search

Perform web searches on DuckDuckGo. Returns normalized results with title, decoded URL, description, hostname, and pagination for any query.

Instructions

Search DuckDuckGo web results. Returns normalized 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. Results are fetched from DuckDuckGo's own server-rendered search page.

Input Schema

TableJSON 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

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds important context: results are normalized, pagination is page-based, and the endpoint always returns decoded destination URLs rather than DuckDuckGo click-tracking redirects. It does not cover rate limits or error behavior, but the core surprising behavior is transparent.

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

Conciseness5/5

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

Three sentences with no waste: the first states the purpose, the second lists return contents and pagination, and the third explains the redirect-decoding behavior. Information is front-loaded and every sentence earns its place.

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?

There is no output schema, so the description usefully enumerates the returned fields (title, destination URL, description, hostname) and pagination. It covers the query requirement and the key URL-decoding behavior. It is slightly incomplete on when to prefer this over sibling search tools and on limits/errors, but is adequate for calling the tool correctly.

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 parameters. The description adds only that results are for a query string and mention page-based pagination; it does not add semantics for region, time_range, or safe_search beyond what the schema already provides. Baseline 3 is appropriate.

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?

The first sentence states a specific verb and resource: 'Search DuckDuckGo web results.' The phrase 'web results' clearly separates it from sibling tools like duckduckgo_image, duckduckgo_news, duckduckgo_shopping, and duckduckgo_video without needing to inspect their schemas.

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 description implies use for general web searches but does not explicitly mention alternatives or state when not to use it. It does not name sibling search tools like duckduckgo_image or duckduckgo_news, leaving the agent to infer the distinction from tool names rather than explicit guidance.

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