HasData

bing_serp: GET /

hasdata_bing_serp_getSearchResults

Read-only

Get Bing Search Results

Fetches Bing SERPs for a query with geo targeting (location/lat/lon), market (mkt), country (cc), safesearch (off/moderate/strict), interface language (setLang), time/custom filters, device type, and pagination (first offset). Returns organic results (title, url, snippet, displayed url, position) and related searches. Use for SEO rank tracking, SERP feature monitoring, Bing-specific visibility audits, and training/eval data for search agents.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Specify the search term for which you want to scrape the SERP.
`cc`	No	The two-letter country code for the country to search from.
`lat`	No	GPS latitude for the search origin.
`lon`	No	GPS longitude for the search origin.
`mkt`	No	The two-letter country code for the country to search from.
`first`	No	This parameter specifies the number of search results to skip and is used for implementing pagination. For example, a value of 1 (default) indicates the first page of results, 11 refers to the second page, and 21 to the third page.
`filters`	No	Allows applying various filters to narrow search results, including date-based options: - `ex1:"ez1"` – past 24 hours - `ex1:"ez2"` – past week - `ex1:"ez3"` – past month For complex filters, run a Bing search and copy the filters parameter from the URL.
`setLang`	No	The language of the user interface and preferred result language. Accepts a two-letter language code (e.g. `en`, `de`) or a locale/script variant (e.g. `en-gb`, `zh-hans`, `pt-br`).
`location`	No	Defines the search’s origin location as free text (e.g. `Austin, Texas`). It is resolved to coordinates to localize the results. For realistic results, set location at the city level. If both `lat` and `lon` are provided, they take precedence and `location` is ignored. If omitted, the proxy’s location may be used.
`deviceType`	No	Specify the device type for the search.
`safeSearch`	No	Adult Content Filtering option.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 8, 2026

removedInput schema / properties / count

Removed value: -{
-  "description": "Number of results per page, ranging from 1 to 50.",
-  "type": "number"
-}

changedInput schema / properties / location / description

Previous value: -"Defines the search’s origin location. For realistic results, set location at the city level. If omitted, the proxy’s location may be used."New value: +"Defines the search’s origin location as free text (e.g. `Austin, Texas`). It is resolved to coordinates to localize the results. For realistic results, set location at the city level. If both `lat` and `lon` are provided, they take precedence and `location` is ignored. If omitted, the proxy’s location may be used."

removedInput schema / properties / safe

Removed value: -{
-  "description": "Adult Content Filtering option.",
-  "enum": [
-    "off",
-    "moderate",
-    "strict"
-  ],
-  "type": "string"
-}

addedInput schema / properties / safeSearch

Added value: +{
+  "description": "Adult Content Filtering option.",
+  "enum": [
+    "off",
+    "moderate",
+    "strict"
+  ],
+  "type": "string"
+}

addedInput schema / properties / setLang

Added value: +{
+  "description": "The language of the user interface and preferred result language. Accepts a two-letter language code (e.g. `en`, `de`) or a locale/script variant (e.g. `en-gb`, `zh-hans`, `pt-br`).",
+  "enum": [
+    "ar",
+    "bg",
+    "ca",
+    "zh-hans",
+    "zh-hant",
+    "hr",
+    "cs",
+    "da",
+    "nl",
+    "en",
+    "en-gb",
+    "et",
+    "fi",
+    "fr",
+    "de",
+    "he",
+    "hi",
+    "hu",
+    "it",
+    "jp",
+    "ko",
+    "lv",
+    "lt",
+    "ms",
+    "nb",
+    "pl",
+    "pt-br",
+    "pt-pt",
+    "ro",
+    "ru",
+    "sr",
+    "sk",
+    "sl",
+    "es",
+    "sv",
+    "th",
+    "tr",
+    "uk",
+    "vi"
+  ],
+  "type": "string"
+}

First observedApr 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, lowering the bar. The description adds genuine behavioral detail: the returned fields (title, url, snippet, displayed url, position) plus related searches, and the location/lat/lon precedence rule. It omits rate limits and rate/error behavior, keeping it from a 5.

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

Conciseness5/5

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

Two tightly packed sentences: purpose first, then parameter scope, return contents, and use cases. Every clause earns its place and nothing is repeated or padded.

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?

With no output schema, the description correctly compensates by describing the return shape (organic results plus related searches). Annotations cover the safety profile and the schema covers all parameters, so the definition is nearly self-sufficient; minor gaps like pagination limits or proxy behavior are not covered.

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 and the schema does the heavy lifting. The description still adds value by grouping the 11 parameters into functional clusters (geo, market, country, safesearch, language, filters, device, pagination), which helps an agent reason about interactions even though the individual semantics live in the 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?

States a specific verb and resource ('Fetches Bing SERPs for a query') and immediately enumerates the functional scope: geo targeting, market, country, safesearch, language, filters, device, and pagination. There are no sibling tools to disambiguate against, but the purpose is unambiguous and complete.

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?

Provides clear positive use cases ('SEO rank tracking, SERP feature monitoring, Bing-specific visibility audits, and training/eval data for search agents'). It gives strong context for when to reach for the tool, but offers no exclusions or alternatives (none exist among siblings), so it stops short of full when/when-not guidance.

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

All HasData 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.

Resources

Need Help?