Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: List Sitemaps

bing_webmaster_list_sitemaps
Read-only

Lists a site's submitted sitemaps and feeds with type, processing status, URL count, size, and last crawl time, so you can audit what Bing has processed.

Instructions

The sitemaps and feeds submitted for the site (top level only), each with its type, processing status, URL count, size and when Bing last crawled it. For the children of a sitemap index, use bing_webmaster_get_sitemap.

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_list_sitemaps"
  }
}

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 sitemaps to return (1-500). Defaults to 100.

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing the return shape (type, processing status, URL count, size, last-crawled time) and the top-level-only depth restriction, which are not derivable from annotations. It does not address how the limit interacts with truncation of a large sitemap set.

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 with no filler; the scope and returned fields come first, and the disambiguation sentence follows. Nothing is repeated from the title or schema.

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 correctly compensates by naming the per-sitemap fields the agent will receive, and it pins down the hierarchy depth. Only minor gaps remain, such as result ordering or what happens when more sitemaps exist than the limit allows.

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%: the site parameter's normalization rules and the limit parameter's 1-500 range are fully documented in the schema. The description's 'top level only' phrase adds depth semantics but says nothing further about limit or site matching beyond what the schema already states, so 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?

States a specific verb and resource (list the sitemaps and feeds submitted for a site), names the exact scope ('top level only'), and enumerates the per-item fields returned. It cleanly separates this from bing_webmaster_get_sitemap, which handles index children.

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?

Explicitly routes the agent to bing_webmaster_get_sitemap when it needs the children of a sitemap index, which is the main ambiguity an agent would face here. It does not offer any other exclusions or prerequisites (e.g. that the site must first be resolvable via bing_webmaster_list_sites), leaving that single alternative as the only piece of guidance.

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