Litescrape

Bing Search

bing_search

Read-only

Get Bing web search results.

Input Schema

Name	Required	Description	Default
`q`	Yes	Bing search query after trimming. Accepted length: 1 through 2,048 characters. Control characters are rejected. Bing query syntax such as quoted phrases and exclusions remains available.
`cc`	No	Case-insensitive two-letter country of origin. Format: US or GB. Cannot be combined with mkt.
`lat`	No	Latitude from -90 through 90. May be supplied independently or with lon.
`lon`	No	Longitude from -180 through 180. May be supplied independently or with lat.
`mkt`	No	Case-insensitive Bing language-country market token. Format: two-letter language and country, such as en-US. Cannot be combined with cc.
`first`	No	One-based native offset for organic results. Range: 1 through 9,007,199,254,740,991. Prefer litescrape_pagination.next when it is returned.
`device`	No	Selects desktop, tablet, or mobile result behavior.	desktop
`engine`	No	Selects the Bing web-search engine.	bing
`filters`	No	Native Bing display or date filter expression. Maximum length: 8,192 characters. Control characters are rejected.
`location`	No	Named city-level origin used to localize the Bing request. Maximum length: 256 characters. Control characters are rejected.
`safeSearch`	No	Bing adult-content policy; values are case-insensitive.	moderate
`result_groups`	No	Return only these top-level result groups, e.g. ["organic_results", "knowledge_graph"]; omit for the complete response. search_metadata is always kept

Schema Changelog

Changes observed during successful MCP inspections.

Changed55 schema fields changedOct 19, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / cc / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / cc / default
```
Added value: +null
```

changedInput schema / properties / cc / description

Previous value: -"Two-letter country code; conflicts with mkt"New value: +"Case-insensitive two-letter country of origin.\n\nFormat: US or GB. Cannot be combined with mkt."

removedInput schema / properties / cc / maxLength
```
Removed value: -2
```
removedInput schema / properties / cc / minLength
```
Removed value: -2
```
addedInput schema / properties / cc / title
```
Added value: +"Cc"
```
removedInput schema / properties / cc / type
```
Removed value: -"string"
```
addedInput schema / properties / device / default
```
Added value: +"desktop"
```

changedInput schema / properties / device / description

Previous value: -"Layout to request; default desktop"New value: +"Selects desktop, tablet, or mobile result behavior."

addedInput schema / properties / device / title
```
Added value: +"Device"
```

addedInput schema / properties / engine

Added value: +{
+  "const": "bing",
+  "default": "bing",
+  "description": "Selects the Bing web-search engine.",
+  "title": "Engine",
+  "type": "string"
+}

addedInput schema / properties / filters / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / filters / default
```
Added value: +null
```

changedInput schema / properties / filters / description

Previous value: -"Native Bing display or date filters"New value: +"Native Bing display or date filter expression.\n\nMaximum length: 8,192 characters. Control characters are rejected."

removedInput schema / properties / filters / maxLength
```
Removed value: -8192
```
addedInput schema / properties / filters / title
```
Added value: +"Filters"
```
removedInput schema / properties / filters / type
```
Removed value: -"string"
```
addedInput schema / properties / first / default
```
Added value: +1
```

changedInput schema / properties / first / description

Previous value: -"One-based organic result offset for pagination; default 1"New value: +"One-based native offset for organic results.\n\nRange: 1 through 9,007,199,254,740,991. Prefer litescrape_pagination.next when it is returned."

removedInput schema / properties / first / minimum
```
Removed value: -1
```
addedInput schema / properties / first / title
```
Added value: +"First"
```

addedInput schema / properties / lat / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / lat / default
```
Added value: +null
```

changedInput schema / properties / lat / description

Previous value: -"Latitude; supply together with lon"New value: +"Latitude from -90 through 90.\n\nMay be supplied independently or with lon."

removedInput schema / properties / lat / maximum
```
Removed value: -90
```
removedInput schema / properties / lat / minimum
```
Removed value: --90
```
addedInput schema / properties / lat / title
```
Added value: +"Lat"
```
removedInput schema / properties / lat / type
```
Removed value: -"number"
```

addedInput schema / properties / location / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / location / default
```
Added value: +null
```

changedInput schema / properties / location / description

Previous value: -"City-level search origin"New value: +"Named city-level origin used to localize the Bing request.\n\nMaximum length: 256 characters. Control characters are rejected."

removedInput schema / properties / location / maxLength
```
Removed value: -256
```
addedInput schema / properties / location / title
```
Added value: +"Location"
```
removedInput schema / properties / location / type
```
Removed value: -"string"
```

addedInput schema / properties / lon / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / lon / default
```
Added value: +null
```

changedInput schema / properties / lon / description

Previous value: -"Longitude; supply together with lat"New value: +"Longitude from -180 through 180.\n\nMay be supplied independently or with lat."

removedInput schema / properties / lon / maximum
```
Removed value: -180
```
removedInput schema / properties / lon / minimum
```
Removed value: --180
```
addedInput schema / properties / lon / title
```
Added value: +"Lon"
```
removedInput schema / properties / lon / type
```
Removed value: -"number"
```

addedInput schema / properties / mkt / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / mkt / default
```
Added value: +null
```

changedInput schema / properties / mkt / description

Previous value: -"Market such as en-US; conflicts with cc"New value: +"Case-insensitive Bing language-country market token.\n\nFormat: two-letter language and country, such as en-US. Cannot be combined with cc."

addedInput schema / properties / mkt / title
```
Added value: +"Mkt"
```
removedInput schema / properties / mkt / type
```
Removed value: -"string"
```

changedInput schema / properties / q / description

Previous value: -"Search query; Bing operators are preserved"New value: +"Bing search query after trimming.\n\nAccepted length: 1 through 2,048 characters. Control characters are rejected. Bing query syntax such as quoted phrases and exclusions remains available."

removedInput schema / properties / q / maxLength
```
Removed value: -2048
```
removedInput schema / properties / q / minLength
```
Removed value: -1
```
addedInput schema / properties / q / title
```
Added value: +"Q"
```
addedInput schema / properties / safeSearch / default
```
Added value: +"moderate"
```

changedInput schema / properties / safeSearch / description

Previous value: -"Default moderate"New value: +"Bing adult-content policy; values are case-insensitive."

addedInput schema / properties / safeSearch / title
```
Added value: +"Safesearch"
```
addedInput schema / title
```
Added value: +"Request"
```

First observedSep 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, covering the safety and nature of the call. The description adds nothing beyond that — no mention of rate limits, result caps, pagination behavior, or what the response contains, despite the schema hinting at pagination via 'litescrape_pagination.next'.

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?

A single front-loaded sentence with zero waste, which is genuinely concise. It is arguably under-specified rather than over-verbose, but it is not padded and gets to the point immediately.

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

Completeness2/5

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

With 12 parameters, no output schema, and locale/market/device/pagination controls, a one-sentence description leaves significant gaps an agent would need to resolve — particularly how to paginate, how cc/mkt interact, and what the response structure looks like.

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%, and the schema documents every parameter in detail, including market/country mutual exclusions, length limits, and pagination offsets. The description contributes no additional parameter meaning, so 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 states a specific verb and resource ('Get Bing web search results'), and naming Bing implicitly distinguishes it from the google_search and duckduckgo_search siblings. However, it never explicitly routes the agent between those alternatives, so it falls short of 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 Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use, and no mention of the sibling search tools (google_search, duckduckgo_search). The agent must infer selection criteria entirely from the tool name.

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

All Litescrape tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Bing Search

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources