Skip to main content
Glama
oki602960

brave-search-mcp-server

by oki602960

brave_web_search

brave_web_search

Search the web using Brave Search API to retrieve comprehensive results with metadata, supporting filters for country, freshness, and content type.

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
countNoNumber of results (1-20, default 10). Applies only to web search results (i.e., has no effect on locations, news, videos, etc.)
queryYesSearch query (max 400 chars, 50 words)
unitsNoThe measurement units. If not provided, units are derived from search country.
offsetNoPagination offset (max 9, default 0)
countryNoSearch query country, where the results come from. The country string is limited to 2 character country codes of supported countries.US
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. Multiple goggle URLs and/or definitions can be provided in an array. For more details, refer to the Goggles repository (i.e., https://github.com/brave/goggles-quickstart).
summaryNoThis parameter enables summary key generation in web search results. This is required for summarizer to be enabled.
ui_langNoThe language of the UI. The 2 or more character language code for which the search results are provided.en-US
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.
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
spellcheckNoWhether to spellcheck the provided query.
search_langNoSearch language preference. The 2 or more character language code for which the search results are provided.en
result_filterNoResult filter (default ['web', 'query'])
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.
text_decorationsNoWhether display strings (e.g. result snippets) should include decoration markers (e.g. highlighting characters).
Behavior3/5

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

Annotations only include 'openWorldHint: true', so the description carries more burden. It discloses return format (JSON list with title, description, URL) and that results can vary based on 'results_filter'. It doesn't discuss rate limits, authentication, or any side effects beyond consumption of the API. Adequate but not thorough.

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?

The description is concise, well-structured with a main sentence, bullet points for use cases, and a note about 'results_filter'. No redundant 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?

For a web search tool with 15 parameters and no output schema, the description covers the purpose, use cases, and key behavioral notes. It could mention that it requires network access (implied by openWorldHint) or pagination behavior, but overall it's fairly complete.

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 parameters are fully described in the schema. The description adds minimal extra meaning, only noting the effect of 'results_filter' on result types. Baseline of 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?

The description clearly states it performs web searches using Brave Search API and lists diverse use cases (general, location, news, videos). It distinguishes from sibling tools by mentioning that when 'results_filter' is empty, results may include FAQ, Discussions, News, and Video, which are normally handled by separate siblings.

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?

The 'When to use' section provides explicit scenarios. It also notes behavior when 'results_filter' is empty, implying when to expect additional result types. However, it does not explicitly mention when NOT to use this tool or list alternatives like brave_local_search or brave_video_search.

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