Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Sitemap

bing_webmaster_get_sitemap
Read-only

Retrieve details for one submitted sitemap, including status, URL count, last crawl time, and, for sitemap indexes, the child sitemaps it points to.

Instructions

Details of one submitted sitemap. For a sitemap index, lists the child sitemaps it points to, each with status, URL count and last crawl.

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>",
      "sitemap_url": "<sitemap_url>"
    },
    "name": "bing_webmaster_get_sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 child sitemaps to return (1-1000). Defaults to 100.
sitemap_urlYesThe sitemap, as bing_webmaster_list_sitemaps reports it, e.g. "https://example.com/sitemap.xml" — an absolute URL, e.g. "https://example.com/pricing".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/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 genuine behavioral context by explaining that for a sitemap index the response expands into child sitemaps with status, URL count and last crawl. It omits what happens for an ordinary sitemap beyond "details," and says nothing about failure or empty cases.

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 sentences, front-loaded with the core purpose, with the index-expansion behavior immediately after. No filler and nothing repeated from the schema or annotations.

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 must convey what comes back, and it does so for the index case; the single-sitemap return fields are only gestured at as "details." Combined with a fully documented schema and read-only annotations, this is close to complete for a simple read tool.

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% and the parameter texts are rich, covering site matching tolerance and sitemap_url format. The description adds no parameter-level meaning, so the baseline 3 applies; the schema, not the prose, carries this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

"Details of one submitted sitemap" states a specific verb (retrieve details) and a specific resource (a single sitemap), and the contrast with a plural lister is implicit in "one submitted sitemap." It does not name bing_webmaster_list_sitemaps explicitly, so sibling differentiation is left to the schema rather than the prose.

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

Usage Guidelines3/5

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

The description implies the use case (inspecting a single sitemap you already know the URL of) but never states when to prefer this over listing sitemaps or how to obtain sitemap_url. Guidance for discovering the URL comes from the schema parameter text, not the description.

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