Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

duckduckgo_news

Search news articles by query and return titles, URLs, sources, excerpts, thumbnails, and times with page-based pagination.

Instructions

Search DuckDuckGo news results. Returns DuckDuckGo news results for a query string: title, destination URL, source, excerpt, thumbnail, and relative/published time, plus page-based pagination.

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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return shape (title, URL, source, excerpt, thumbnail, time) and that pagination is page-based, which is useful. However it says nothing about rate limits, freshness/recency behavior, or result caps, so behavioral disclosure is partial.

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?

Two sentences, purpose first, no padding. The second sentence is a dense field list but it earns its place given there is no output schema. Slightly run-on but efficient.

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 simple 3-parameter search tool with no output schema, the description covers purpose, result fields, and pagination, which is most of what an agent needs. Missing only usage differentiation and behavioral limits like rate caps.

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 q, page, and region with defaults and examples. The description mentions 'query string' and 'page-based pagination' but adds no syntax, format, or constraint detail beyond the schema. 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?

States a specific verb ('Search') and resource ('DuckDuckGo news results'), and the result fields listed (title, source, excerpt, thumbnail, time) make it unambiguous what kind of content is returned. It doesn't explicitly differentiate from the sibling duckduckgo_search (general web) or the many other *_news tools, so it stops short of a 5.

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 use this versus duckduckgo_search, duckduckgo_video, or any of the dozens of other news siblings. No prerequisites or exclusions are stated; the agent must infer usage entirely from the name.

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