Skip to main content
Glama
Sign In

SEO and Keyword Data API

by com.duoleads.keywords
OverviewDiscussionsAdmin

Bing search results (10, 20 or 50)

bing_search
Read-onlyIdempotent

Bing search results for a query: the organic results (rank, title, URL, domain, snippet), related searches and the page's result types, for 10, 20 or 50 results in 94 countries and Bing's 49 languages, from Bing search results, $0.018 a call. Use when checking rankings on Bing (and the engines it feeds). Titles and snippets are the pages' own text: untrusted. Search operators are a free 400. Bad input is a free 400; a data source failure is not charged. Price: $0.018 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "bing_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query, at most 200 characters. Search operators (site:, inurl:, quotes, -word, ...) are refused free.
numNoResults: 10, 20 or 50. Default 10.
langNoLanguage code (a Bing language: en, en-GB, de, fr, es, pt-BR, ...). Default: the country's main language when offered, else en.
countryNoISO 3166-1 alpha-2 country code (us, gb, de, ...; uk = gb). Default us.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds genuinely new behavioral facts: results carry the pages' own untrusted text, pricing is $0.018 per successful call with the x402/USDC-on-Base payment mechanism and the _meta key. It also explains the billing edge cases (search operators and bad input are free 400s, a data source failure is not charged), which is exactly the kind of cost/failure semantics annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and return fields are front-loaded, which is good, but the text is a run-on chain of clauses and repeats itself: 'from Bing search results' echoes the opening, and the price appears twice ('$0.018 a call' and 'Price: $0.018 per successful call'). Tightening the price and the 400-policy statements into one place would preserve all the information at half the length.

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?

There is no output schema, so the description must carry the return shape, and it does by naming the result fields, related searches and result types. Combined with cost, payment, untrusted-content and error-charging details, an agent has everything needed to call this correctly for a 4-parameter read 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?

Schema description coverage is 100%, so both optional parameters and the query constraint are already documented with defaults and ranges. The description only restates the 10/20/50 counts and the 94-country/49-language coverage, adding breadth context but no syntax or meaning beyond the schema, so the baseline 3 applies.

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?

The description names a concrete verb and resource ('Bing search results for a query') and enumerates the returned fields (rank, title, URL, domain, snippet, related searches, result types), so the agent knows exactly what it gets. It distinguishes itself from google_search only indirectly ('Use when checking rankings on Bing (and the engines it feeds)') rather than naming the sibling, which keeps it just below a 5.

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

Usage Guidelines4/5

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

'Use when checking rankings on Bing (and the engines it feeds)' gives a clear selection context against the many Google-oriented siblings in this server. There is no explicit when-not guidance or named alternative (e.g., 'for Google SERPs use google_search'), so it stops short of full routing guidance.

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

All SEO and Keyword Data API 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