Skip to main content
Glama

duckduckgo_search

Retrieve organic search results from DuckDuckGo with support for region codes, date filters, and pagination using next page tokens.

Instructions

Retrieves organic search results from DuckDuckGo with support for region codes, date filters, and pagination via next page tokens. [Credits: Not specified in documentation] Notes: Documentation page does not state a per-request credit cost (unlike Bing Search/Shopping, Universal Search, and ChatGPT Scraper). Response text in the doc's example description referenced 'Google page' for the html param, likely a documentation copy-paste artifact — applies to the DuckDuckGo result page. Returns: { organic_results: [ { title, displayed_link, link, snippet, rank } ], next_page_token }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dfNoFilters results by date. Allowed values: d (Past day), w (Past week), m (Past month), y (Past year). Custom range format: from_date..to_date (e.g., 2021-06-15..2024-06-16).
klNoRegion for the DuckDuckGo search, e.g., us-en for the United States, uk-en for the United Kingdom, fr-fr for France. See DuckDuckGo Supported Regions documentation page.
htmlNoReturns the full HTML of the (DuckDuckGo) page. (default: false)
queryYesThe search query. Any terms or operators normally used in a standard DuckDuckGo search (e.g., inurl:, site:, intitle:, etc.).
next_page_tokenNoToken used to fetch subsequent results. Each page returns 15 results.
Behavior3/5

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

With no annotations, the description carries full burden. It describes return format and pagination but does not explicitly state read-only nature or any side effects. The documentation note is about a copy-paste artifact, not behavioral.

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 detailed and well-structured, front-loading the core purpose and then adding notes. It is slightly lengthy but each part adds information.

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?

Given no output schema, the description thoroughly explains the return format and pagination tokens. It covers query, filters, region, pagination, and HTML retrieval, making it self-contained for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 5 parameters are documented in schema (100% coverage). The description adds extra context: custom date range format, region documentation reference, and clarification on the html param, providing value beyond the schema.

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 description clearly states it retrieves organic search results from DuckDuckGo and lists key features (region codes, date filters, pagination), differentiating it from sibling search tools like Google or Bing.

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 explicit guidance on when to use DuckDuckGo vs alternatives (e.g., Google, Bing). Mentions credit cost differences but does not provide decision criteria for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server