Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Fetched URL

bing_webmaster_get_fetched_url
Read-only

Retrieve the Bingbot fetch result for a URL—HTTP status, response headers, and HTML received—or omit the URL to list fetched pages.

Instructions

The result of a live Bingbot fetch (requested with bing_webmaster_fetch_url, or from the dashboard's URL Inspection): status, response headers and the HTML Bingbot received. Without url, lists the URLs fetched so far. A fetch takes a minute or two to complete after it is requested.

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": {
      "site": "<site>"
    },
    "name": "bing_webmaster_get_fetched_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe fetched page. Omit to list every fetched URL — an absolute URL, e.g. "https://example.com/pricing".
siteYesThe site, e.g. "example.com" or "https://www.example.com/". Matched against the sites this API key reaches (bing_webmaster_list_sites), tolerating a missing scheme, www. or trailing slash; an ambiguous or unknown site is refused with the list of accessible ones.
limitNoMaximum fetched URLs, when listing to return (1-500). Defaults to 50.
max_document_charsNoHow much of the fetched HTML to return (0 for none). Defaults to 2000; document_length says how long the whole page is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Read-only and open-world safety are already covered by the annotations, and the description goes further by disclosing that the tool exposes response headers and the raw HTML Bingbot received, plus the asynchronous delay between request and availability. What it omits is the failure state when a fetch has not completed yet or has errored, which is the main remaining behavioral unknown.

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?

Three short sentences, front-loaded with what is returned, followed by the mode switch and the timing caveat. Every clause carries information an agent needs; nothing is repeated from the name or title.

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 does the necessary work of naming the return contents (status, headers, HTML) and the delay before results exist. Given the fully documented input schema and read-only annotations, it is close to complete, with only pending/error-state behavior left unaddressed.

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 all four parameters are already documented, including the omission-of-`url` listing behavior and the HTML truncation control. The description restates the `url` mode switch but adds no syntax, defaults, or edge-case 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('the result of a live Bingbot fetch') and enumerates the payload: status, response headers and the received HTML. It also distinguishes the two modes (URL given vs omitted) and names the sibling that initiates the fetch (bing_webmaster_fetch_url), so an agent can tell it apart without opening any schema.

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?

It clearly states the two usage modes ('Without `url`, lists the URLs fetched so far') and ties the tool to its prerequisite flow via bing_webmaster_fetch_url or dashboard URL Inspection. It adds a timing note ('a minute or two') that implicitly tells the agent to wait before reading. It does not explicitly say what to do if the fetch is still pending, 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.