Skip to main content
Glama
brave

Brave Search MCP Server

Official

brave_local_search

brave_local_search

Searches for local businesses and places, returning details like addresses, ratings, phone numbers, and hours. Ideal for location-based queries like 'near me' or specific cities.

Instructions

Brave Local Search API provides enrichments for location search results. Access to this API is available only through the Brave Search API Pro plans; confirm the user's plan before using this tool (if the user does not have a Pro plan, use the brave_web_search tool). Searches for local businesses and places using Brave's Local Search API. Best for queries related to physical locations, businesses, restaurants, services, etc.

Returns detailed information including:
    - Business names and addresses
    - Ratings and review counts
    - Phone numbers and opening hours

Use this when the query implies 'near me', 'in my area', or mentions specific locations (e.g., 'in San Francisco'). This tool automatically falls back to brave_web_search if no local results are found.

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).
Behavior4/5

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

Annotations only include title and openWorldHint, so description carries full burden. It discloses plan restriction, automatic fallback to web search, and output fields. No contradictions; minor extra context like rate limits could enhance, but current is sufficient.

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?

Well-structured with key info upfront: introduction, plan requirement, purpose, output, usage guidance, and fallback. Slightly lengthy but every sentence adds value.

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?

Covers purpose, input hints, output fields, plan restrictions, and fallback. Without output schema, the description adequately explains what the tool returns. Could mention more about response structure but sufficient.

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 has 100% parameter description coverage, so baseline 3 is appropriate. The description adds no additional meaning to parameters beyond what the schema already provides.

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 searches for local businesses and places using Brave's Local Search API, and distinguishes from siblings like brave_web_search by specifying the types of queries (e.g., 'near me', specific locations) and plan requirements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (location queries) and when not to use (if user lacks Pro plan, use brave_web_search). Provides concrete examples of query types and mentions fallback behavior.

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