Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

bing_news

Search Bing news articles by query and return structured JSON results for news monitoring, with US English defaults and page/count options.

Instructions

Search Bing news results. Returns Bing news search results for a query string. Locale defaults to country=us and lang=en-us. Returns 503 when Bing serves a challenge page or unusable results.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
langNoBing UI language; defaults to en-us
pageNo1-based page number; defaults to 1
countNoResults per page; defaults to 10, clamped to 1..50
countryNoTwo-letter country code; defaults to us

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose a useful failure mode: 'Returns 503 when Bing serves a challenge page or unusable results.' That is real behavioral context. However, it says nothing about rate limits, throttling beyond the 503, or result structure/pagination semantics for what is effectively a network-fetch tool.

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 compact sentences, front-loaded with purpose, then locale defaults, then failure behavior. The first two sentences are slightly redundant ('Search Bing news results' vs 'Returns Bing news search results'), but overall there is little waste.

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?

No output schema exists, so the description should carry the return shape, and it only says it 'Returns Bing news search results' without describing fields or structure. It covers the failure mode and defaults, but leaves the agent without a picture of the payload for a search tool whose schema is otherwise complete.

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%, so the baseline is 3. The description only restates locale defaults (country=us, lang=en-us) that the schema already documents in each property, adding no format, range, or interaction detail beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Search Bing news results' / 'Returns Bing news search results for a query string.' The 'Bing news' qualifier distinguishes it from the generic bing_search, but the description never names or contrasts against siblings like bing_search, brave_news, or duckduckgo_news, so an agent still has to infer why to pick this over those.

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

Usage Guidelines2/5

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

No when-to-use guidance at all. It does not say when to prefer Bing news over bing_search, brave_news, or google_news_search, nor any prerequisites or exclusions. Only implied usage ('search news') is available.

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

Deploy Server

Other Tools