Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Request

bing_webmaster_request
Read-only

Use 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

NameRequiredDescriptionDefault
bodyNoJSON body for a POST, e.g. {"siteUrl": "https://example.com/", "blockedUrl": {...}}.
httpNoHTTP verb. Defaults to GET for Get* methods and POST for the rest, which is what Bing expects; a wrong verb answers 405.
paramsNoQuery 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_charsNoCut the answer to this many characters of JSON (an array keeps whole items). Defaults to 20000.
method_nameYesThe API method, PascalCase and case-sensitive, e.g. "GetCrawlSettings" or "GetBlockedUrls".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations, it discloses verb selection and the 405 failure mode, siteUrl normalization to the registered form, response normalization (d envelope unwrapped, __type dropped, dates ISO) yet unshaped output, truncation at max_chars, and the write-disable gate. The one tension is that readOnlyHint=true while the description describes a path to enabling writes, though the default behavior it describes is still read-only.

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?

Front-loaded with the escape-hatch purpose and the key alternative, then packed with operational detail in a few dense sentences. It is long but nearly every clause carries non-obvious behavior; the method-name examples list is slightly bloaty but still illustrative.

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?

For a 5-parameter open-world passthrough with nested objects and no output schema, it covers invocation shape, auth caveat, verb mapping, truncation, and response normalization. An agent has enough to call it correctly without trial and error.

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 already 100%, but the description adds real routing meaning: params go with Get* GETs, body goes with POSTs, params must never contain the API key, and a siteUrl in either is resolved to its registered form. That goes meaningfully beyond the field descriptions.

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 precise role: an escape hatch for calling any Bing Webmaster API method that lacks a dedicated tool, with concrete example method names and a link to the method reference. It explicitly differentiates itself from the named siblings by telling the agent to prefer the dedicated tools, so the boundary is unambiguous.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (no dedicated tool exists), when-not (prefer the dedicated tools), and the operational gate (only Get* methods allowed; writes require BING_WEBMASTER_ALLOW_WRITES=1). The GET-versus-POST rule based on method prefix is also spelled out, so an agent can act without inference.

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