brave

News search

brave_news_search

Read-only

Searches for news articles using Brave's News Search API. Use it when you need current news, breaking updates, or articles about specific topics.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Search query (max 400 characters and 50 words).
`count`	No	Number of results to return (max 20; default 20).
`offset`	No	Pagination offset (max 9, in units of `count`).
`country`	No	2-letter country code (ISO 3166-1 alpha-2). Defaults to US.
`ui_lang`	No	User interface language for the response, in the form <lang>-<country> (e.g. en-US).
`freshness`	No	Filter results by recency. Use pd (past day), pw (past week), pm (past month), py (past year), or a YYYY-MM-DDtoYYYY-MM-DD range.
`safesearch`	No	Filter level for adult content.
`spellcheck`	No	Whether to spellcheck the query.
`search_lang`	No	2-letter language code for the search. Defaults to en.
`text_decorations`	No	Whether to include decoration markers (e.g. highlighting) in result strings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedMay 9, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / count / default
```
Removed value: -20
```

changedInput schema / properties / count / description

Previous value: -"Number of results (1-50, default 20)"New value: +"Number of results to return (max 20; default 20)."

removedInput schema / properties / count / maximum
```
Removed value: -50
```
removedInput schema / properties / count / minimum
```
Removed value: -1
```

changedInput schema / properties / count / type

Previous value: -"integer"New value: +"number"

removedInput schema / properties / country / default
```
Removed value: -"US"
```

changedInput schema / properties / country / description

Previous value: -"Search query country, where the results come from. The country string is limited to 2 character country codes of supported countries."New value: +"2-letter country code (ISO 3166-1 alpha-2). Defaults to US."

removedInput schema / properties / extra_snippets

Removed value: -{
-  "default": false,
-  "description": "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.",
-  "type": "boolean"
-}

removedInput schema / properties / freshness / anyOf

Removed value: -[
-  {
-    "const": "pd",
-    "type": "string"
-  },
-  {
-    "const": "pw",
-    "type": "string"
-  },
-  {
-    "const": "pm",
-    "type": "string"
-  },
-  {
-    "const": "py",
-    "type": "string"
-  },
-  {
-    "type": "string"
-  }
-]

removedInput schema / properties / freshness / default
```
Removed value: -"pd"
```

changedInput schema / properties / freshness / description

Previous value: -"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."New value: +"Filter results by recency. Use pd (past day), pw (past week), pm (past month), py (past year), or a YYYY-MM-DDtoYYYY-MM-DD range."

addedInput schema / properties / freshness / type
```
Added value: +"string"
```

removedInput schema / properties / goggles

Removed value: -{
-  "description": "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).",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / offset / default
```
Removed value: -0
```

changedInput schema / properties / offset / description

Previous value: -"Pagination offset (max 9, default 0)"New value: +"Pagination offset (max 9, in units of `count`)."

removedInput schema / properties / offset / maximum
```
Removed value: -9
```
removedInput schema / properties / offset / minimum
```
Removed value: -0
```

changedInput schema / properties / offset / type

Previous value: -"integer"New value: +"number"

addedInput schema / properties / q

Added value: +{
+  "description": "Search query (max 400 characters and 50 words).",
+  "type": "string"
+}

removedInput schema / properties / query

Removed value: -{
-  "description": "Search query (max 400 chars, 50 words)",
-  "maxLength": 400,
-  "type": "string"
-}

removedInput schema / properties / safesearch / default
```
Removed value: -"moderate"
```

changedInput schema / properties / safesearch / description

Previous value: -"Filters 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'."New value: +"Filter level for adult content."

removedInput schema / properties / search_lang / default
```
Removed value: -"en"
```

changedInput schema / properties / search_lang / description

Previous value: -"Search language preference. The 2 or more character language code for which the search results are provided."New value: +"2-letter language code for the search. Defaults to en."

removedInput schema / properties / spellcheck / default
```
Removed value: -true
```

changedInput schema / properties / spellcheck / description

Previous value: -"Whether to spellcheck provided query."New value: +"Whether to spellcheck the query."

addedInput schema / properties / text_decorations

Added value: +{
+  "description": "Whether to include decoration markers (e.g. highlighting) in result strings.",
+  "type": "boolean"
+}

removedInput schema / properties / ui_lang / default
```
Removed value: -"en-US"
```

changedInput schema / properties / ui_lang / description

Previous value: -"User interface language preferred in response. Usually of the format <language_code>-<country_code>. For more, see RFC 9110."New value: +"User interface language for the response, in the form <lang>-<country> (e.g. en-US)."

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "q"
+]

AddedMay 1, 2026
RemovedMay 1, 2026
AddedApr 26, 2026
RemovedApr 25, 2026
AddedApr 2, 2026
RemovedApr 2, 2026
AddedMar 24, 2026
RemovedMar 24, 2026
AddedMar 24, 2026
RemovedMar 24, 2026

Changed4 schema fields changedMar 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / safesearch / anyOf

Removed value: -[
-  {
-    "const": "off",
-    "type": "string"
-  },
-  {
-    "const": "moderate",
-    "type": "string"
-  },
-  {
-    "const": "strict",
-    "type": "string"
-  }
-]

addedInput schema / properties / safesearch / enum

Added value: +[
+  "off",
+  "moderate",
+  "strict"
+]

addedInput schema / properties / safesearch / type
```
Added value: +"string"
```

First observedJan 31, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=false, destructiveHint=false, and openWorldHint=true. The description adds no behavioral details beyond stating it uses Brave's News Search API (which is a source, not behavior). It does not mention rate limits, result structure, or account requirements. With annotations providing the safety profile, the description adds minimal extra value.

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 consists of two sentences: the first states the main function, the second provides usage guidance. Every word is purposeful, no fluff. It is well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, and the description does not explain the return format (e.g., list of articles with title, source, date). It also does not mention pagination mechanics beyond the 'count' and 'offset' parameters. Given the tool has multiple parameters and is a search tool, the description could be more complete about what the agent can expect as output.

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 description coverage is 100%, meaning all 10 parameters are described in the schema. The tool description does not add any additional parameter semantics or contextual hints beyond what the schema already provides. 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 the verb 'searches' and the resource 'news articles using Brave's News Search API'. It also provides usage context ('when you need current news, breaking updates, or articles about specific topics'), which differentiates it from sibling tools like brave_web_search or brave_image_search.

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 explicitly advises when to use the tool ('when you need current news, breaking updates, or articles about specific topics'). It does not specify when not to use it or name alternatives, but the context implies that for general web or image searches, other brother tools should be used. This is clear enough for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All brave tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

News search

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources