Skip to main content
Glama
Sign In

Brave Search

by io.github.pipeworx-io
OverviewDiscussionsAdmin

News Search

news_search
Read-onlyIdempotent

News-specific search with publication metadata. Returns title, URL, source, age, snippet, and breaking-news flag.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "stock market news"
    },
    "name": "news_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
countNoResults (1-20, default 10)
offsetNo0-9 page offset
countryNo2-letter country code
freshnessNopd | pw | pm | py
search_langNo2-letter language

Output Schema

NameRequiredDescriptionDefault
queryYesThe search query
resultsYesArray of news search results
returnedYesNumber of news results returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "q": "stock market news"
+  },
+  {
+    "count": 10,
+    "country": "gb",
+    "freshness": "pd",
+    "q": "technology companies earnings",
+    "search_lang": "en"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "query": {
+      "description": "The search query",
+      "type": "string"
+    },
+    "results": {
+      "description": "Array of news search results",
+      "items": {
+        "properties": {
+          "age": {
+            "description": "Age of the article",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "breaking": {
+            "description": "Whether article is breaking news",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Article snippet/description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "page_age": {
+            "description": "Age of the page",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source": {
+            "description": "News source hostname",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "thumbnail": {
+            "description": "Article thumbnail image URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "News article title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "News article URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of news results returned",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "query",
+    "returned",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, establishing safe read behavior. The description adds value beyond annotations by specifying return fields and mentioning 'publication metadata' and 'breaking-news flag.' Some behavioral details (e.g., rate limits, pagination) are omitted but not critical given the safety profile.

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 two sentences, front-loaded with the core purpose, and every word adds value. No fluff or redundancy.

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 the presence of an output schema and high schema coverage, the description is sufficient for most use cases. It explains what is returned but could briefly mention how parameters like 'freshness' affect results. Still, it avoids gaps for a news-search tool.

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?

The input schema has 100% coverage with descriptions for all 6 parameters. The description does not add any parameter-specific information beyond what the schema already provides, so the score is at baseline.

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 is a 'News-specific search' tool, specifies the verb 'search' and resource 'news', and lists exact return fields (title, URL, source, age, snippet, breaking-news flag). This distinguishes it from sibling tools like 'web_search' by emphasizing news focus and metadata.

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

Usage Guidelines3/5

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

The term 'News-specific search' implies use for news queries, but no explicit guidance on when to use this vs. alternatives like 'web_search' or when not to use it. No exclusion criteria or alternative tool names are mentioned.

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

All Brave Search toolsInspect
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.

Resources