Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bing_search

Search Bing web results for a query, returning organic links, related queries, people-also-ask, news, video modules, and paginated pages. Use for general web search; site: queries are unsupported.

Instructions

Search Bing web results. Returns Bing web search results for a query string, including organic results, optional context panel data, related queries, people-also-ask questions, news modules, video modules, and page-based pagination. Empty optional blocks are omitted from the JSON response. Locale defaults to country=us and lang=en-us. Returns 503 on a genuine transport failure or challenge page. Bing occasionally serves a well-formed page whose results share no significant term with the query; when every attempt hits this, the response is still returned as 200 with data.low_confidence set to true (and the X-Low-Confidence header) instead of being withheld, so callers get Bing's real answer plus an honest signal to double-check it rather than nothing. Queries that use the site: operator (for example site:gov.hu) are not supported: Bing serves a bot-verification challenge for them, so they are rejected with 400 before any request is made. Use the DuckDuckGo (/api/v1/duckduckgo/search), Brave (/api/v1/brave/search), or Yahoo (/api/v1/yahoo-search/search) search endpoints for domain-restricted searches instead.

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. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations to lean on, the description carries the full behavioral burden and does so richly: it discloses the 503 transport/challenge failure mode, the 200 + data.low_confidence + X-Low-Confidence header degraded-result behavior, the 400 pre-flight rejection for site: queries, and the omission of empty optional blocks. This is exactly the failure-mode context an agent needs before trusting a response.

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?

Purpose is front-loaded in the first sentence and every subsequent sentence earns its place by carrying a distinct failure mode or scoping rule. It is dense and runs long, but there is little waste given the tool's complexity.

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?

For a multi-module search tool with no output schema, the description accurately enumerates the response shape (organic results, context panel, related queries, people-also-ask, news/video modules) and all significant error/degradation paths, so an agent can both call it and interpret its output correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds the concrete locale defaults (country=us, lang=en-us) as a single coherent statement, marginally reinforcing the schema's per-field defaults. It does not add syntax or format detail beyond what the schema already documents for page/count.

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 opening verb+resource ("Search Bing web results") is specific and immediately distinguishes this from the many sibling search tools by naming the explicit alternatives (DuckDuckGo/Brave/Yahoo) for domain-restricted queries. An agent can route correctly without opening any 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?

Explicitly states the condition that disqualifies this tool (site: operator queries rejected with 400) and names the three alternative endpoints to use instead, giving a full when/when-not/alternative picture. Nothing is left to inference.

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