Skip to main content
Glama
oki602960

brave-search-mcp-server

by oki602960

brave_news_search

brave_news_search

Search for news articles with real-time results. Get headlines and summaries from current events and specific topics.

Instructions

This tool searches for news articles using Brave's News Search API based on the user's query. Use it when you need current news information, breaking news updates, or articles about specific topics, events, or entities.

When to use:
    - Finding recent news articles on specific topics
    - Getting breaking news updates
    - Researching current events or trending stories
    - Gathering news sources and headlines for analysis

Returns a JSON list of news-related results with title, url, and description. Some results may contain snippets of text from the article.

When relaying results in markdown-supporting environments, always cite sources with hyperlinks.

Examples:
    - "According to [Reuters](https://www.reuters.com/technology/china-bans/), China bans uncertified and recalled power banks on planes".
    - "The [New York Times](https://www.nytimes.com/2025/06/27/us/technology/ev-sales.html) reports that Tesla's EV sales have increased by 20%".
    - "According to [BBC News](https://www.bbc.com/news/world-europe-65910000), the UK government has announced a new policy to support renewable energy".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results (1-50, default 20)
queryYesSearch query (max 400 chars, 50 words)
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).
ui_langNoUser interface language preferred in response. Usually of the format <language_code>-<country_code>. For more, see RFC 9110.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' - Filter out explicit content. 'strict' - Filter out explicit and suggestive content. The default value is 'moderate'.moderate
spellcheckNoWhether to spellcheck provided query.
search_langNoSearch language preference. The 2 or more character language code for which the search results are provided.en
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.
Behavior3/5

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

Annotations only include title and openWorldHint (unclear). The description adds behavioral info: returns JSON list with title, url, description, and snippets. No contradictions, but no disclosure on rate limits or authentication. Since annotations are minimal, the description provides adequate but not rich behavioral context.

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?

The description is somewhat lengthy but well-structured into sections (purpose, when to use, result format, examples). It is front-loaded with the core purpose. Could be slightly more concise, but generally clear and organized.

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 11 parameters, no output schema, and no nested objects, the description explains the return format (JSON list with title, url, description, snippets) and provides usage guidance. It covers essential context but could mention pagination more explicitly (offset and count).

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 covers 100% of parameters with descriptions, so the description does not need to add much. It summarizes query and result format, but adds no new parameter details beyond the schema. Baseline 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 searches for news articles using Brave's News Search API. It distinguishes from sibling tools (other Brave searches) by specifying 'news' and providing usage examples, making the purpose specific and unambiguous.

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 description includes a 'When to use' list that explicitly guides the agent on appropriate scenarios (e.g., finding recent news, breaking updates). It also provides markdown citation examples. While it lacks explicit 'when not to use', the positive guidance is strong and contextually clear.

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