Skip to main content
Glama
oki602960

brave-search-mcp-server

by oki602960

brave_image_search

brave_image_search

Searches for images using Brave Search API to find visual content including photos, design ideas, and art 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.
Behavior2/5

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

Annotations only provide 'openWorldHint: true', which signals non-destructive but no further details. Description adds a markdown display tip but lacks disclosure of rate limits, authentication needs, pagination specifics, or error behavior.

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?

Two concise sentences: first states purpose, second offers usage advice. No wasted words, front-loaded with key information.

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?

Output schema exists, so return values are covered. Description adds practical usage advice (markdown images) and covers the tool's typical context. Could mention pagination via 'offset' (covered in schema) but otherwise complete for a simple search tool.

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 explains all parameters. The description does not add additional parameter-level meaning beyond what is in the schema, earning a baseline score.

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?

Clearly states action ('performs an image search') and resource ('Brave Search API'). Provides specific examples of use cases (pictures, design, art) and implicitly distinguishes from sibling tools like web, local, news searches.

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?

Gives examples of when to use ('when you need pictures...') but does not explicitly state when not to use or mention alternatives. The sibling list helps, but the description itself lacks direct guidance on differentiation.

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/oki602960/brave-search-mcp-server'

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