Brave Search MCP Server

Official

Overview Schema Related Servers Score Discussions(1)

brave_web_search

brave_web_search

Search the web via Brave Search API to get comprehensive results with rich metadata such as titles, descriptions, URLs, and filters for news, videos, discussions, FAQ, and locations.

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

Name	Required	Description	Default
`count`	No	Number of results (1-20, default 10). Applies only to web search results (i.e., has no effect on locations, news, videos, etc.)
`query`	Yes	Search query (max 400 chars, 50 words)
`units`	No	The measurement units. If not provided, units are derived from search country.
`offset`	No	Pagination offset (max 9, default 0)
`country`	No	Search query country, where the results come from. The country string is limited to 2 character country codes of supported countries.	US
`goggles`	No	Goggles 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).
`summary`	No	This parameter enables summary key generation in web search results. This is required for summarizer to be enabled.
`ui_lang`	No	The language of the UI. The 2 or more character language code for which the search results are provided.	en-US
`freshness`	No	Filters 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.
`safesearch`	No	Filters 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
`spellcheck`	No	Whether to spellcheck the provided query.
`search_lang`	No	Search language preference. The 2 or more character language code for which the search results are provided.	en
`result_filter`	No	Result filter (default ['web', 'query'])
`extra_snippets`	No	A 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_decorations`	No	Whether display strings (e.g. result snippets) should include decoration markers (e.g. highlighting characters).

Schema Changelog

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

Changed1 schema field 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"

Changed11 schema fields changedv2.0.66Apr 30, 2026

addedInput schema / $schema

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

addedInput schema / properties / freshness / anyOf

Added value: +[
+  {
+    "enum": [
+      "pd",
+      "pw",
+      "pm",
+      "py"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}to\\d{4}-\\d{2}-\\d{2}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / freshness / enum

Removed value: -[
-  "pd",
-  "pw",
-  "pm",
-  "py",
-  "YYYY-MM-DDtoYYYY-MM-DD"
-]

removedInput schema / properties / freshness / type
```
Removed value: -"string"
```

addedInput schema / properties / goggles / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

changedInput schema / properties / goggles / description

Previous value: -"Goggles 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)."New value: +"Goggles 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)."

removedInput schema / properties / goggles / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / goggles / type
```
Removed value: -"array"
```

addedInput schema / properties / units / anyOf

Added value: +[
+  {
+    "const": "metric",
+    "type": "string"
+  },
+  {
+    "const": "imperial",
+    "type": "string"
+  }
+]

removedInput schema / properties / units / enum

Removed value: -[
-  "metric",
-  "imperial"
-]

removedInput schema / properties / units / type
```
Removed value: -"string"
```

First observedv1.0.0Sep 23, 2025

TDQS

A4/5.0

Behavior2/5

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

The description does not disclose any behavioral traits beyond the action of performing a search. It does not mention whether the operation is read-only, any rate limits, authentication requirements, or side effects, which is a significant gap given the lack of readOnlyHint or destructiveHint annotations.

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, with a clear opening statement, a bulleted list of use cases, and a note about results_filter. The structure is well-organized and easy to scan without unnecessary verbosity.

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?

The description gives a high-level overview of the return value ('comprehensive search results with rich metadata') and includes usage scenarios. While it does not detail the output structure (no output schema exists), it provides enough context to understand the tool's function and key behaviors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides thorough descriptions for all parameters (100% coverage), and the description adds extra context, such as the behavior of result_filter when empty and how it affects returned result types. This goes beyond the schema's generic description.

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 the tool's purpose: performing web searches via the Brave Search API and returning comprehensive results. It distinguishes itself from sibling search tools by explicitly mentioning 'web searches' and the general nature of the results.

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 lists several concrete scenarios, such as general web searches, location-based queries, and news searches. However, it does not explicitly contrast with sibling tools (e.g., when to use local search instead), leaving some ambiguity about edge cases.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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