Litescrape

DuckDuckGo Search

duckduckgo_search

Read-only

Get DuckDuckGo web search results.

Input Schema

Name	Required	Description	Default
`m`	No	Requested result count from 1 through 50; mutually exclusive with search_assist.
`q`	Yes	Required search text, up to 500 characters.
`df`	No	Date window: d, w, m, y, or YYYY-MM-DD..YYYY-MM-DD.
`kl`	No	DuckDuckGo region and language token, such as us-en.
`safe`	No	DuckDuckGo safe-search level.	-1
`start`	No	Result offset from 0 through 10,000.
`result_groups`	No	Return only these top-level result groups, e.g. ["organic_results", "knowledge_graph"]; omit for the complete response. search_metadata is always kept
`search_assist`	No	Enable DuckDuckGo query assistance; mutually exclusive with m.

Schema Changelog

Changes observed during successful MCP inspections.

Changed33 schema fields changedOct 19, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / df / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / df / default
```
Added value: +null
```

changedInput schema / properties / df / description

Previous value: -"Date filter: d, w, m, y, or YYYY-MM-DD..YYYY-MM-DD"New value: +"Date window: d, w, m, y, or YYYY-MM-DD..YYYY-MM-DD."

addedInput schema / properties / df / title
```
Added value: +"Df"
```
removedInput schema / properties / df / type
```
Removed value: -"string"
```

addedInput schema / properties / kl / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / kl / default
```
Added value: +null
```

changedInput schema / properties / kl / description

Previous value: -"Region and language token such as us-en"New value: +"DuckDuckGo region and language token, such as us-en."

removedInput schema / properties / kl / maxLength
```
Removed value: -32
```
addedInput schema / properties / kl / title
```
Added value: +"Kl"
```
removedInput schema / properties / kl / type
```
Removed value: -"string"
```
addedInput schema / properties / m / default
```
Added value: +50
```

changedInput schema / properties / m / description

Previous value: -"Result count 1-50; cannot be combined with search_assist"New value: +"Requested result count from 1 through 50; mutually exclusive with search_assist."

removedInput schema / properties / m / maximum
```
Removed value: -50
```
removedInput schema / properties / m / minimum
```
Removed value: -1
```
addedInput schema / properties / m / title
```
Added value: +"M"
```

changedInput schema / properties / q / description

Previous value: -"Search query"New value: +"Required search text, up to 500 characters."

removedInput schema / properties / q / maxLength
```
Removed value: -500
```
removedInput schema / properties / q / minLength
```
Removed value: -1
```
addedInput schema / properties / q / title
```
Added value: +"Q"
```
addedInput schema / properties / safe / default
```
Added value: +"-1"
```

changedInput schema / properties / safe / description

Previous value: -"1 strict, -1 moderate (default), -2 off"New value: +"DuckDuckGo safe-search level."

addedInput schema / properties / safe / title
```
Added value: +"Safe"
```
addedInput schema / properties / search_assist / default
```
Added value: +true
```

changedInput schema / properties / search_assist / description

Previous value: -"Default true; cannot be combined with m"New value: +"Enable DuckDuckGo query assistance; mutually exclusive with m."

addedInput schema / properties / search_assist / title
```
Added value: +"Search Assist"
```
addedInput schema / properties / start / default
```
Added value: +0
```

changedInput schema / properties / start / description

Previous value: -"Result offset"New value: +"Result offset from 0 through 10,000."

removedInput schema / properties / start / maximum
```
Removed value: -10000
```
removedInput schema / properties / start / minimum
```
Removed value: -0
```
addedInput schema / properties / start / title
```
Added value: +"Start"
```
addedInput schema / title
```
Added value: +"Request"
```

First observedSep 15, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on rate limits, result freshness, whether results are cached, or how pagination via 'start' behaves in practice.

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?

A single short sentence with no wasted words and the key noun front-loaded. It is efficient, though it errs toward under-specification rather than genuine conciseness.

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?

This is an 8-parameter tool with an open-world, non-idempotent profile and no output schema; the description does not compensate for that complexity by describing usage context, result shape, or engine-selection tradeoffs. The annotation and schema carry nearly all the weight.

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 all 8 parameters (including enum, defaults, and mutual-exclusion notes like m vs search_assist) are already documented in the schema. The description contributes no additional parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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?

The description names a verb (Get) and a resource (DuckDuckGo web search results), so the basic purpose is clear. However, it is essentially a restatement of the title and offers no differentiation from the sibling search tools (google_search, bing_search, google_maps), leaving the agent to guess which engine's results it returns.

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 guidance on when to choose this tool over google_search or bing_search, no mention of prerequisites, and no exclusions. The description supplies no usage context at all beyond the bare purpose.

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

All Litescrape tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

DuckDuckGo Search

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources