Crawlora MCP

brave_images

Read-only

Returns normalized Brave image search results for a query string. Locale defaults to country=us and lang=en-us. Results are fetched from public Brave Search image 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_search to search Brave.

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real operational context beyond them: results come from scraped public HTML and the tool returns 503 when Brave serves a challenge page. That failure-mode disclosure is genuinely useful, though nothing is said about rate limits or result stability.

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

Conciseness3/5

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

Reasonably front-loaded, but the 'Query: Search query. Required, e.g. openai. Count: Results to return, default 10, clamped to 1..50' sentences duplicate the schema verbatim and don't earn their place. The valuable 503 note is buried mid-paragraph.

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?

With an output schema present, the description need not explain return values, and the 503/challenge note plus locale defaults cover the main behavioral surprises. It is nearly complete for an 8-param read tool, lacking only clearer routing guidance among the many sibling search tools.

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 all eight parameters. The description restates Query and Count semantics but adds nothing on DateFrom/DateTo/TimeRange pairing, Offset paging, Country, or Language beyond what the schema says. 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 and resource: returns normalized Brave image search results for a query. It names a sibling (brave_search) and the underlying source (public Brave Search image HTML), so an agent can distinguish it from generic web search tools 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 Guidelines3/5

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

The closing line 'Use brave_search to search Brave' gestures at an alternative, but it is ambiguous — it doesn't clarify when to pick image search over brave_search, brave_news, brave_videos, or other image providers like bing_images. Usage is only implied by the tool's resource.

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.