Brave Search MCP Server

Official

Overview Schema Source Related Servers Discussions(1)Admin

brave_image_search

brave_image_search

Search for images of people, places, things, graphic design ideas, and art inspiration. Retrieve image results with configurable count, country, and safe search settings.

Instructions

Performs an image search using the Brave Search API. Helpful for when you need pictures of people, places, things, graphic design ideas, art inspiration, and more. When relaying results in a markdown environment, it may be helpful to include images in the results (e.g., ![image.title](image.properties.url)).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No	Number of results (1-200, default 50). Image Search is not paginated — raise `count` if you need more results. There is no `offset` parameter.
`query`	Yes	The user's search query. Query cannot be empty. Limited to 400 characters and 50 words.
`country`	No	Search query country, where the results come from. The country string is limited to 2 character country codes of supported countries.	US
`safesearch`	No	Filters search results for adult content. The following values are supported: 'off' - No filtering. 'strict' - Drops all adult content from search results.	strict
`spellcheck`	No	Whether to spellcheck provided query.
`search_lang`	No	Search language preference. The 2 or more character language code for which the search results are provided.	en

Output Schema

TableJSON Schema

Name	Required	Description
`type`	Yes
`count`	Yes
`items`	Yes
`might_be_offensive`	Yes	Whether the image might be offensive.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.1.4Sep 18, 2026

changedInput schema / properties / count / description

Previous value: -"Number of results (1-200, default 50). Combine this parameter with `offset` to paginate search results."New value: +"Number of results (1-200, default 50). Image Search is not paginated — raise `count` if you need more results. There is no `offset` parameter."

Changed2 schema fields changedv2.1.3Aug 21, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed8 schema fields changedv2.0.66Apr 30, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / safesearch / anyOf

Added value: +[
+  {
+    "const": "off",
+    "type": "string"
+  },
+  {
+    "const": "strict",
+    "type": "string"
+  }
+]

removedInput schema / properties / safesearch / enum
```
Removed value: -[
-  "off",
-  "strict"
-]
```
removedInput schema / properties / safesearch / type
```
Removed value: -"string"
```
addedOutput schema / properties / count / maximum
```
Added value: +9007199254740991
```

addedOutput schema / properties / items / items / properties / page_fetched / pattern

Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"

addedOutput schema / properties / items / items / properties / properties / properties / height / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / items / items / properties / properties / properties / width / maximum
```
Added value: +9007199254740991
```

First observedv1.0.0Sep 23, 2025

TDQS

A3.5/5.0

Behavior3/5

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

Annotations are minimal (only title and openWorldHint=true), so the description carries most of the behavioral disclosure burden. It discloses the API source (Brave Search API) and a useful result-format characteristic (markdown image embedding). It does not mention rate limits, authentication, error behavior, or what happens with zero results, but the markdown hint adds genuine behavioral context beyond the annotations.

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?

The description is appropriately brief: three sentences covering purpose, use cases, and a practical markdown tip. The core purpose and use cases are front-loaded, and the markdown hint, while tangential, is actionable and earns its place. There is no redundant or filler text.

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?

Given the rich input schema (100% parameter coverage, defaults, constraints) and presence of an output schema, the description is sufficiently complete. It covers what the tool does, when to use it, and adds a practical result-format hint. The main gap is the lack of explicit rate-limit or error behavior context, but the schema and output schema cover most operational needs.

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 six parameters with types, defaults, constraints, and descriptions. The description adds only the markdown URL format hint, which is not a parameter semantic. Baseline 3 is appropriate because the schema carries the parameter documentation burden, and the description neither conflicts with nor meaningfully extends the schema.

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?

Description clearly states a specific verb and resource: 'Performs an image search using the Brave Search API.' The use cases ('pictures of people, places, things, graphic design ideas, art inspiration') help distinguish it from generic search, but it does not explicitly differentiate from sibling tools like brave_video_search or brave_web_search. The purpose is unambiguous, with differentiation implied by the name and use cases.

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 description gives concrete use cases for when to use image search ('when you need pictures...') and a practical markdown embedding tip. However, it provides no explicit guidance on when not to use this tool or when a sibling like brave_video_search or brave_web_search would be more appropriate. The intended usage context is clear but exclusions/alternatives are not stated.

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

Deploy Server