Submit up to 500 URLs to Bing for indexing in one batch request. Specify the site URL and a list of URLs to expedite indexing.
Submit multiple URLs to Bing for indexing in a single batch
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The URL of the site | |
| urlList | Yes | List of URLs to submit (max 500) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description lacks details on side effects, rate limits, authentication requirements, or whether the submission is immediate or queued.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no redundancy, front-loaded key information (action, target, batch nature).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Missing output schema and description—agent cannot know success/failure details, error handling, or per-URL status. Batch semantics require more info.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Adds value by noting urlList max 500, supplementing the schema descriptions that are already present for both parameters (100% coverage).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'Submit multiple URLs to Bing for indexing in a single batch', distinguishing it from single URL submission tools like bing_url_submit and quota tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies use for batch submission of multiple URLs, but no explicit guidance on when to use vs alternatives like index_now or when not to use (e.g., if site not verified).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.