Skip to main content
Glama

Bing News Search

bing_news_search
Read-onlyIdempotent

Keyword news search via Bing News RSS, keyless. Returns recent matching articles with title, the real article link (decoded from Bing's tracking redirect, not the redirect itself), publish time, source publication and a short description. Independent of Google News (country_news pack) and GDELT (gdelt pack), a different vendor on different infrastructure, useful as a corroborating source or when either of those is down.

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": {
      "count": 5,
      "query": "\"Series A\" funding"
    },
    "name": "bing_news_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
numNoAlias of count.
countNoNumber of articles wanted, an upper bound (1-50, default 20). Aliases accepted: limit, num, max_results. When Bing's first page is short the pack widens through its date-sorted and recent-window views, de-duplicated and keeping only articles that contain a query word, until the count is met or the source is exhausted; the response carries requested, returned and exhausted.
limitNoAlias of count.
queryYesSearch keywords, e.g. "Series A funding"
max_resultsNoAlias of count.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Alias of count.",
      +  "type": "number"
      +}
    • addedInput schema / properties / max_results
      Added value: +{
      +  "description": "Alias of count.",
      +  "type": "number"
      +}
    • addedInput schema / properties / num
      Added value: +{
      +  "description": "Alias of count.",
      +  "type": "number"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "limit": 5,
      -    "query": "\"Series A\" funding"
      -  }
      -]New value: +[
      +  {
      +    "count": 5,
      +    "query": "\"Series A\" funding"
      +  }
      +]
    • addedInput schema / properties / count
      Added value: +{
      +  "description": "Number of articles wanted, an upper bound (1-50, default 20). Aliases accepted: limit, num, max_results. When Bing's first page is short the pack widens through its date-sorted and recent-window views, de-duplicated and keeping only articles that contain a query word, until the count is met or the source is exhausted; the response carries requested, returned and exhausted.",
      +  "type": "number"
      +}
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Max items to return (1-50, default 20)",
      -  "type": "number"
      -}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description still adds real value beyond them: it discloses the keyless auth model and warns that links are decoded out of Bing's tracking redirect, which is material to how results should be used. Pagination/rate-limit behavior is left to the schema rather than restated here.

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?

Three sentences, front-loaded with the verb and the access model, and no filler. It is dense—the return-value sentence packs five fields into one clause—but each clause carries information an agent needs.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the returned fields (title, resolved link, publish time, source, short description). Combined with the auth note and the alternative-source guidance, an agent has everything needed to call it correctly.

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 coverage is 100% and the count property already documents the alias set (limit, num, max_results), the 1-50 bound, and the widening/de-duplication strategy. The description adds essentially no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Keyword news search via Bing News RSS'), plus the key differentiator 'keyless'. It explicitly names the other vendors (Google News / country_news pack, GDELT / gdelt pack) and how this one differs in vendor and infrastructure, so an agent can place it without opening a schema.

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?

Gives concrete routing guidance: use it as a corroborating source, or as a fallback when Google News or GDELT is down. The conditions that select this tool over the alternatives are stated rather than implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.