Crawlora MCP

brave_search

Read-only

Search Brave's public web results by Query, returning ranked links and any included related queries or knowledge card. Offset is a zero-based result page; use TimeRange or paired DateFrom/DateTo for date filtering. Country defaults to us and Language to en-us. Use brave_news for news-only results.

Input Schema

Name	Required	Description
`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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety posture is covered. The description adds real context beyond that: the return shape (ranked links, related queries, knowledge card) and the default values for Country (us) and Language (en-us).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence earns its place: scope, return shape, pagination, date filtering, defaults, and the sibling escape hatch, all front-loaded with zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 needn't be exhaustively described, and the description still summarizes them. With 100% param coverage, annotations, and sibling routing all present, nothing an agent needs to call this correctly is missing.

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 7 parameters including the Offset/TimeRange/default semantics. The description restates the Offset page meaning and date pairing rather than adding new syntax or constraints, so baseline 3 is appropriate.

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+resource ('Search Brave's public web results') and immediately distinguishes itself from the sibling brave_news for news-only results. An agent can route web vs. news queries without opening a 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?

Explicitly names brave_news as the alternative for news-only results and gives date-filter guidance (TimeRange or paired DateFrom/DateTo). It stops short of clarifying when to prefer brave_images or brave_videos, so routing vs. those siblings is left to inference.

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.