Crawlora MCP

brave_videos

Read-only

Returns normalized Brave video search results for a query string. Locale defaults to country=us and lang=en-us. Results are fetched from public Brave Search video HTML and return 503 when Brave serves a challenge page or unusable HTML. Query: Search query. Required, e.g. openai. Count: Results to return, default 10, clamped to 1..50. Use brave_images to search Brave image results.

Input Schema

Name	Required	Description
`Count`	No	Results to return, default 10, clamped to 1..50.
`Query`	Yes	Search query. Required, e.g. openai.
`DateTo`	No	Custom end date in YYYY-MM-DD; required when time_range=custom, must pair with date_from.
`Offset`	No	Zero-based Brave result page; minimum 0, default 0.
`Country`	No	Brave result country, default us. Allowed values: all, ar, at, au, be, br, ca, ch, cl, cn, de, dk, es, fi, fr, gb, gr, hk, id, in, it, jp, kr, mx, my, nl, no, nz, ph, pl, pt, ru, sa, se, sg, tr, tw, us, za.
`DateFrom`	No	Custom start date in YYYY-MM-DD; required when time_range=custom, must pair with date_to.
`Language`	No	Brave UI language, default en-us. Allowed values: de-de, en-ca, en-gb, en-in, en-us, fi-fi, fr-ca, fr-fr, ja-jp, pt-br, sq-al, sw-ke, zh-tw.
`TimeRange`	No	Preset time filter. Allowed values: any, day, week, month, year, custom.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations cover safety (readOnlyHint, openWorldHint), and the description adds genuinely useful operational context: results come from public Brave video HTML and a 503 is returned on challenge pages or unusable HTML. That error-behavior disclosure goes beyond what annotations provide.

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?

Front-loaded with the core purpose before the locale and error details. Slightly repetitive in re-listing Query and Count, which the schema already documents, but overall tight.

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?

An output schema exists, so return values need no explanation, and annotations plus the 503/HTML-source note cover the runtime profile. The only gap is any explicit statement of when this tool beats its search siblings.

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 baseline is 3. The description restates Query and Count (already documented in the schema) and mentions locale defaults that also appear in the Country/Language schema descriptions, adding no new parameter meaning.

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?

States a specific verb and resource ('Returns normalized Brave video search results') and explicitly distinguishes itself from the sibling brave_images. An agent can identify the tool's role without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Points to brave_images as the alternative for image results, which implies this tool is for video results. However, it never states when-not to use this tool or when videos are preferable to brave_search/general search, so routing is implied rather than explicit.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.