Skip to main content
Glama

bing_submit_url_batch

Submits up to 500 URLs per batch to Bing for indexing as a fallback to IndexNow, helping you get multiple pages discovered without submitting them individually.

Instructions

Submit multiple URLs to Bing for indexing (max 500 per batch). Use IndexNow as primary method; this is a fallback.

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>",
      "urls": "<urls>"
    },
    "name": "bing_submit_url_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesArray of URLs to submit (max 500)
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It usefully discloses a hard batch ceiling of 500 URLs, but says nothing about authentication requirements, quota consumption against Bing submission limits, partial-failure behavior, or whether resubmission is idempotent.

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 short sentences with no filler; purpose and the size limit come first, and the fallback routing lands where an agent needs it before selecting the tool. Nothing is redundant or buried.

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?

For a two-parameter mutation tool with no output schema and no annotations, the description covers what it does, its batch limit, and its position relative to the primary IndexNow path. Remaining gaps are operational details like quota impact and failure semantics rather than anything blocking correct invocation.

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 both parameters are already documented in the schema, including the 500-item cap on urls. The description restates the same constraint rather than adding new meaning such as required URL format, domain-matching rules against siteUrl, or duplicate handling.

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 ("Submit multiple URLs to Bing for indexing") plus a scope bounding detail (max 500 per batch). The concluding clause routes it clearly away from indexnow_submit_batch, so an agent can distinguish it from siblings without opening schemas.

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 declares the preferred alternative and the condition that selects it: IndexNow is primary, this is the fallback. It does not address when to use the single-URL variant (bing_submit_url) instead of this batch form, so the routing guidance is strong but not exhaustive.

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