Skip to main content
Glama

bing_submit_sitemap

Submits a sitemap URL to Bing Webmaster Tools so site pages can be discovered and indexed more reliably.

Instructions

Submit a sitemap to Bing Webmaster Tools.

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": {
      "siteUrl": "<siteUrl>",
      "feedUrl": "<feedUrl>"
    },
    "name": "bing_submit_sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedUrlYesThe sitemap URL to submit
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It says nothing about whether the call requires an authenticated/verified site, whether re-submitting the same sitemap is idempotent, whether it replaces or adds to existing sitemaps, or what a failure looks like.

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?

A single, front-loaded sentence with no filler, which is appropriate for a simple two-parameter action. The brevity borders on under-specification rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the definition should at least cover prerequisites and expected outcome. As written, the agent knows the action but not the conditions for success or the response, which is a meaningful gap.

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%, with both siteUrl and feedUrl documented in the schema itself, so the baseline is 3. The description adds no extra meaning about the relationship between the site and the sitemap URL or accepted URL formats.

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?

The description gives a specific verb and resource ('Submit a sitemap to Bing Webmaster Tools'), so an agent immediately knows what action is performed. It does not, however, distinguish this from sibling submission tools such as bing_submit_url or indexnow_submit_url, leaving the sitemap-vs-URL distinction to inference.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the URL submission tools or IndexNow alternatives, and no stated prerequisites such as a verified site or configured API credentials. The agent is left to infer the entire selection context.

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