Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get URL Info

bing_webmaster_get_url_info
Read-only

Inspect any page or domain in Bing's index to confirm whether it is known, its last HTTP status, crawl dates, document size, and child URL count—more reliable than a site: search.

Instructions

Bing's URL inspection for one page: whether Bing knows it, the HTTP status it last got, when it was discovered and last crawled, document size, anchor count, and how many URLs Bing knows below it. Prefer this over a site: web search to check whether Bing has a page — a search result is neither complete nor current. url may also be "domain:example.com" for the whole domain.

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>",
      "url": "<url>"
    },
    "name": "bing_webmaster_get_url_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page, e.g. "https://example.com/pricing", or "domain:example.com" for the domain.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds substantive value by disclosing what the response contains and warning that web-search proxies are stale/incomplete, which shapes trust in the output. It stops short of describing error modes for inspection failures (those are partly handled by the `site` schema text), so it is not fully complete.

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 tight sentences: what it returns, when to prefer it, and the alternate URL form. Nothing is padded and the highest-value information (the list of returned fields) is front-loaded.

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?

There is no output schema, and the description compensates by enumerating the returned fields, so an agent knows what to expect. For a two-parameter read-only inspection tool with rich schema text and annotations, nothing material is missing.

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 coverage is 100%, including the `domain:example.com` form and the tolerant site matching, so the schema already carries parameter semantics. The description's `url` sentence largely restates the schema and adds no new syntax or constraints, making the baseline 3 appropriate.

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 opens with a specific verb+resource ("URL inspection for one page") and then enumerates the exact data points returned: Bing's awareness, last HTTP status, discovery/crawl dates, document size, anchor count, and known child URLs. That level of specificity lets an agent distinguish it from siblings like get_fetched_url or get_url_links without inspecting schemas.

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?

It gives an explicit when-to-use rule: prefer this over a `site:` web search to check whether Bing has a page, with the reason that search results are neither complete nor current. It also states the domain-level alternative form of the `url` parameter, so the agent knows both granularities are supported by this one tool.

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