Skip to main content
Glama

bing_search

Retrieve organic Bing search results with customizable geographic location, localization, pagination, and content filtering parameters.

Instructions

Retrieves organic search results from Bing with customizable parameters for geographic location, localization, pagination, and content filtering. [Credits: 5 API credits per request] Notes: Endpoint costs 5 API credits per request. lat/lon set a geographic starting point; mkt and cc are mutually exclusive localization options. Returns: { bing_data: [ { title, displayed_link, link, snippet, rank, images[] } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCountry from which the search is conducted, using two-character ISO 3166-1 format (e.g., 'us', 'de', 'gb').
latNoGPS latitude as the starting point for the search.
lonNoGPS longitude as the starting point for the search.
mktNoMarket from which the results originate, formatted as <language code>-<country code> (e.g., en-US), case-insensitive. Mutually exclusive with cc.
countNoNumber of results displayed per page, ranging from 1 to 50 maximum. Actual results may vary.
firstNoAdjusts the starting position of organic search results. Setting first=10 shifts the 10th result to first position. (default: 1)
queryYesThe search query, allowing any terms or operators used in a standard Bing search (e.g., 'query', NOT, OR, site:, filetype:, near:, ip:, loc:, feed:, etc.).
filtersNoEnables advanced filtering options such as date range filtering or specific display filters. Construct values by copying filters from a Bing search URL.
safeSearchNoControls filtering level for adult content. Allowed values: Off, Moderate, Strict.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the credit cost, mutual exclusivity of mkt and cc, and the return format. However, it omits details like rate limits, auth requirements, or error handling. The added context is valuable but not exhaustive.

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?

The description is reasonably concise with two sentences plus a notes section. It front-loads the purpose and adds essential details. Slight repetition of credit cost could be removed, but overall efficient.

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 9 parameters and no output schema, the description covers the return format and key parameter interactions. It lacks details on pagination behavior or error cases, but for a search tool it provides sufficient context for an agent to use it 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%, baseline 3. The description adds meaning beyond the schema by explaining that lat/lon set a geographic starting point, mkt and cc are mutually exclusive, and first adjusts starting position with a default. This improves usability beyond the raw schema.

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 retrieves organic search results from Bing with customizable parameters, using a specific verb and resource. It implicitly distinguishes from sibling tools like Bing Shopping and other search engines by explicitly naming Bing search.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or compare to related sibling tools like google_search, duckduckgo_search, etc.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server