Skip to main content
Glama

duckduckgo

by com.jojapi
OverviewDiscussionsAdmin

Search

get

DuckDuckGo web search: the organic results (url, title, plain and HTML snippet, result types, host, sublinks, date, site name, rating) and the other blocks of the same answer: ads, related searches, the knowledge panel, the AI answer when DuckDuckGo gives it inline, and the news, image and video strips. Blocks DuckDuckGo did not send are empty lists or null. Billing per call: 1 Credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesThe search query.
pageNoThe results page, from 1. The first page holds 10 results, every later page 15; positions continue across pages.
timeNoOnly results from the past day, week, month or year, or from a date range YYYY-MM-DD..YYYY-MM-DD.
regionNoA DuckDuckGo region code such as us-en, de-de or uk-en; wt-wt is no region.
safe_searchNoDuckDuckGo's default is moderate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / page
      Added value: +{
+  "description": "The results page, from 1. The first page holds 10 results, every later page 15; positions continue across pages.",
+  "example": 2,
+  "title": "Page",
+  "type": "integer"
+}
    • changedInput schema / properties / q / description
      Previous value: -"You can use DuckDuckGo search parameters."New value: +"The search query."
    • changedInput schema / properties / q / example
      Previous value: -"Nike"New value: +"nikola tesla"
    • addedInput schema / properties / region
      Added value: +{
+  "description": "A DuckDuckGo region code such as us-en, de-de or uk-en; wt-wt is no region.",
+  "example": "us-en",
+  "title": "Region",
+  "type": "string"
+}
    • addedInput schema / properties / safe_search
      Added value: +{
+  "description": "DuckDuckGo's default is moderate.",
+  "enum": [
+    "strict",
+    "moderate",
+    "off"
+  ],
+  "title": "Safe Search",
+  "type": "string"
+}
    • addedInput schema / properties / time
      Added value: +{
+  "description": "Only results from the past day, week, month or year, or from a date range YYYY-MM-DD..YYYY-MM-DD.",
+  "example": "week",
+  "title": "Time",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "q"
+]
  2. First observed

TDQS

A3.5/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 and does real work: it discloses per-call billing (1 Credit) and the important semantic that absent blocks come back as empty lists or null rather than being omitted. It does not cover authentication, rate limits, or whether a query can fail, so it falls short of exhaustive, but the added behavioral context is substantial.

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 clause, followed by return-shape detail that earns its place given there is no output schema. The long parenthetical field enumeration is dense and slightly run-on, but it is information-bearing rather than padding.

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?

For a no-output-schema tool, the description compensates well by describing both the organic result fields and the secondary blocks, plus null/empty semantics. The notable gap is routing versus the five sibling verticals, which an agent needs to pick the right tool.

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 five parameters (q, page, time, region, safe_search) are already documented in the schema, including pagination semantics and region codes. The description adds nothing about parameters, so the baseline 3 applies.

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?

The opening clause 'DuckDuckGo web search' gives a clear verb and resource, and the rest enumerates exactly what the answer contains. However, it never distinguishes this general search from siblings like get_news, get_images or get_videos, even though it claims to return news, image and video strips — an overlap an agent could easily misread.

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 guidance at all: no mention of when to prefer this over get_news/get_images/get_videos, no prerequisites, no exclusions. The only actionable statement is the billing note, which is a cost fact rather than usage guidance.

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

All duckduckgo toolsInspect
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.

Resources