Bing Webmaster: Request
bing_webmaster_requestUse as a fallback to call any Bing Webmaster API GET method lacking a dedicated tool, passing method name and parameters for normalized read-only results.
Instructions
Escape hatch: call any Bing Webmaster API method that has no dedicated tool, by name — e.g. GetBlockedUrls, GetCrawlSettings, GetQueryParameters, GetSiteRoles, GetSiteMoves, GetUrlTrafficInfo, GetChildrenUrlInfo, GetKeyword, GetQueryPageDetailStats. Methods: https://learn.microsoft.com/en-us/dotnet/api/microsoft.bing.webmaster.api.interfaces.iwebmasterapi. Get* methods are GET with params in params; everything else is POST with a JSON body. A siteUrl in params or body is resolved to its registered form first. The answer is normalized (the d envelope unwrapped, __type dropped, dates ISO) but not shaped, and cut at max_chars — prefer the dedicated tools. Writes are DISABLED: only Get* methods are allowed. Set BING_WEBMASTER_ALLOW_WRITES=1 to allow others.
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": {
"method_name": "<method_name>"
},
"name": "bing_webmaster_request"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | JSON body for a POST, e.g. {"siteUrl": "https://example.com/", "blockedUrl": {...}}. | |
| http | No | HTTP verb. Defaults to GET for Get* methods and POST for the rest, which is what Bing expects; a wrong verb answers 405. | |
| params | No | Query parameters for a GET, named as in the API reference (camelCase), e.g. {"siteUrl": "example.com", "url": "https://example.com/a"}. Never the API key. | |
| max_chars | No | Cut the answer to this many characters of JSON (an array keeps whole items). Defaults to 20000. | |
| method_name | Yes | The API method, PascalCase and case-sensitive, e.g. "GetCrawlSettings" or "GetBlockedUrls". |