Skip to main content
Glama
Sign In
Bing Webmaster Tools MCP Server

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

submit_url_batch

Submit multiple site URLs for indexing in a single request. Check your URL submission quota to confirm the maximum number of URLs allowed per batch.

Instructions

Submit multiple URLs for indexing in a single request.

The max number of urls that can be submitted in a batch is 500 unless it exceeds the available quota. get_url_submission_quota should be called to determine how much urls can be submitted.

Args: site_url: The URL of the site url_list: List of URLs to submit

Raises: BingWebmasterError: If URLs cannot be submitted

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_url": "<site_url>",
      "url_list": "<url_list>"
    },
    "name": "submit_url_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYes
url_listYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • removedInput schema / properties / self
      Removed value: -{
-  "title": "self",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "self",
-  "site_url",
-  "url_list"
-]New value: +[
+  "site_url",
+  "url_list"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "null"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "submit_url_batchOutput",
+  "type": "object"
+}
  3. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the 500 URL max, the quota check, and an error case, but does not disclose whether the batch is atomic, how partial failures are handled, or any side effects. This is insufficient for a write operation.

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?

The description is concise and well-structured, front-loading the primary purpose, then adding the limit, quota note, args, and error. It avoids unnecessary detail and is easy to parse.

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

Completeness3/5

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

The description covers the core action, batch limit, quota dependency, and error behavior. However, it omits prerequisites like site verification, whether the operation is synchronous, and any success response semantics (though output schema exists, so return format is not required). It is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description is the only source for parameter meaning. It provides only trivial descriptions ('The URL of the site' and 'List of URLs to submit') that essentially restate the parameter names without adding constraints, URL format, or prerequisites.

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 clearly states it submits multiple URLs for indexing in a single request, which directly distinguishes it from the single-URL submit_url sibling. The verb and resource are specific, though it doesn't explicitly name the alternative.

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?

It provides a clear usage guideline by advising to call get_url_submission_quota to determine the allowable number of URLs, which is a concrete step. However, it does not explicitly state when to prefer this over submit_url or other submission tools, nor any exclusions.

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

Deploy Server

Other Tools