Skip to main content
Glama
brave

Brave Search MCP Server

Official
by brave
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Remote

brave_image_search

brave_image_search

Find images by performing an image search. Use it to retrieve picture results for people, places, things, and design inspiration.

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
NameRequiredDescriptionDefault
countNoNumber of results (1-200, default 50). Combine this parameter with `offset` to paginate search results.
queryYesThe user's search query. Query cannot be empty. Limited to 400 characters and 50 words.
countryNoSearch query country, where the results come from. The country string is limited to 2 character country codes of supported countries.US
safesearchNoFilters search results for adult content. The following values are supported: 'off' - No filtering. 'strict' - Drops all adult content from search results.strict
spellcheckNoWhether to spellcheck provided query.
search_langNoSearch language preference. The 2 or more character language code for which the search results are provided.en

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
countYes
itemsYes
might_be_offensiveYesWhether the image might be offensive.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv2.1.3
    • 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"
  2. Changed8 schema fields changedv2.0.66
    • 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
  3. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With only openWorldHint in annotations, the description carries most of the behavioral burden. It does clarify the result is an image search and provides practical Markdown-formatting guidance, but it does not disclose any authentication, quota, network, or side-effect caveats. For a safe read-only search tool, this is adequate but not rich.

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 compact and front-loaded: the core purpose is in the first sentence, and the use-cases plus Markdown example are additive rather than redundant. The sentence has a slight looseness ('and more') but still every sentence earns its place.

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?

For a network image search tool with a detailed input schema and output schema, the description provides all the main common use cases and a helpful Markdown display tip. It lacks only an explicit routing to sibling search tools, but the schema and output schema already cover the technical details an agent 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?

The schema description coverage is 100% and all six parameters already have thorough descriptions, defaults, and bounds. The tool description adds no extra parameter-level meaning, so it remains at the baseline score of 3 for parameter semantics.

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?

The description immediately states a specific verb+resource: 'Performs an image search using the Brave Search API.' The use cases (people, places, design ideas) make its scope unmistakable and distinguish it from the sibling web, video, news, and local search tools without ambiguity.

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?

It offers concrete guidance on when to use the tool: when pictures of people, places, things, art inspiration, or design ideas are requested. However, it does not explicitly tell the agent when not to use it or steer it toward a sibling alternative, so it falls one short of a full 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brave/brave-search-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server