Skip to main content
Glama
dodou

brave-search-mcp

by dodou

brave_web_search

brave_web_search

Search the web for general information, news, videos, discussions, and local businesses. Returns comprehensive results with titles, descriptions, URLs, and optional filters for country, language, freshness, and safe search.

Instructions

Performs web searches using the Brave Search API and returns comprehensive search results with rich metadata.

When to use:
    - General web searches for information, facts, or current topics
    - Location-based queries (restaurants, businesses, points of interest)
    - News searches for recent events or breaking stories
    - Finding videos, discussions, or FAQ content
    - Research requiring diverse result types (web pages, images, reviews, etc.)

Returns a JSON list of web results with title, description, and URL.

When the "results_filter" parameter is empty, JSON results may also contain FAQ, Discussions, News, and Video results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (max 400 chars, 50 words)
countryNoSearch query country, where the results come from. The country string is limited to 2 character country codes of supported countries.US
search_langNoSearch language preference. The 2 or more character language code for which the search results are provided.en
ui_langNoThe language of the UI. The 2 or more character language code for which the search results are provided.en-US
countNoNumber of results (1-20, default 10). Applies only to web search results (i.e., has no effect on locations, news, videos, etc.)
offsetNoPagination offset (max 9, default 0)
safesearchNoFilters search results for adult content. The following values are supported: 'off' - No filtering. 'moderate' - Filters explicit content (e.g., images and videos), but allows adult domains in search results. 'strict' - Drops all adult content from search results. The default value is 'moderate'.moderate
freshnessNoFilters search results by when they were discovered. The following values are supported: 'pd' - Discovered within the last 24 hours. 'pw' - Discovered within the last 7 days. 'pm' - Discovered within the last 31 days. 'py' - Discovered within the last 365 days. 'YYYY-MM-DDtoYYYY-MM-DD' - Timeframe is also supported by specifying the date range e.g. 2022-04-01to2022-07-30.
text_decorationsNoWhether display strings (e.g. result snippets) should include decoration markers (e.g. highlighting characters).
spellcheckNoWhether to spellcheck the provided query.
result_filterNoResult filter (default ['web', 'query'])
gogglesNoGoggles act as a custom re-ranking on top of Brave's search index. The parameter supports both a url where the Goggle is hosted or the definition of the Goggle. For more details, refer to the Goggles repository (i.e., https://github.com/brave/goggles-quickstart).
unitsNoThe measurement units. If not provided, units are derived from search country.
extra_snippetsNoA snippet is an excerpt from a page you get as a result of the query, and extra_snippets allow you to get up to 5 additional, alternative excerpts. Only available under Free AI, Base AI, Pro AI, Base Data, Pro Data and Custom plans.
summaryNoThis parameter enables summary key generation in web search results. This is required for summarizer to be enabled.
Behavior4/5

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

Annotations only have openWorldHint, so description carries burden. It explains that results_filter empty triggers extra result types (FAQ, Discussions, News, Video) beyond the core web results. This adds useful behavioral context beyond what annotations provide.

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?

Description is concise: one sentence for purpose, bullet list for use cases, then return format and special behavior. Every sentence earns its place, no fluff. Front-loaded with the main action.

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 15 parameters and no output schema, the description covers return format (JSON list with title, desc, URL) and a key behavioral nuance (empty results_filter). It could detail more about other result types, but overall is sufficient for a 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 coverage is 100%, so baseline is 3. Description adds that count only affects web results (already in schema) and behavior of results_filter when empty (not in schema). This minor addition justifies maintaining the baseline without penalty.

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?

The description states it performs web searches and returns comprehensive results. It lists specific use cases but includes location-based queries, which are better served by a sibling tool (brave_local_search), potentially confusing the agent. Overall purpose is clear but slightly diluted by broad 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 provides a 'When to use' list including general searches, local, news, videos, etc., but does not explicitly compare with sibling tools or state when not to use. It implies context but lacks exclusions or alternatives.

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

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