Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

duckduckgo_video

Search DuckDuckGo video results by query to retrieve titles, URLs, descriptions, durations, thumbnails, publishers, publish dates, view counts, and page-based results.

Instructions

Search DuckDuckGo video results. Returns DuckDuckGo video results for a query string: title, destination URL, description, duration, thumbnail, publisher/uploader, published time, and view count, 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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses the return fields and that pagination is page-based, which is real added context. However, it says nothing about rate limits, auth requirements, or how results are ordered, so meaningful behavioral gaps remain.

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?

It is essentially two sentences, front-loaded with the core purpose before the field list. The enumerated return fields are slightly verbose but each earns its place by describing output that has no schema, so waste is minimal.

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?

Since there is no output schema, the description usefully enumerates the return fields, and it covers the query and pagination dimensions. It is reasonably complete for a simple search tool, though the region parameter and result ordering remain unaddressed.

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 coverage is 100%, so the schema already documents all three parameters, making 3 the baseline. The description echoes the query string and page-based pagination but adds no syntax or format detail, and never addresses the region parameter at all.

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 description states a specific verb ("Search") and resource ("DuckDuckGo video results") and lists the returned fields, so an agent knows exactly what this does. It is clearly the video variant of the duckduckgo_* family, but it never explicitly names or contrasts with siblings like duckduckgo_search or youtube_search.

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?

Usage is only implied by the verb and resource — there is no statement of when to choose this over duckduckgo_search (web), duckduckgo_news, or other video search tools like youtube_search. No exclusions or prerequisites are given, leaving the agent to infer that this is for video-result queries.

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