Skip to main content
Glama
Sign In
mcp-server-bing-webmaster

mcp-server-bing-webmaster

by isiahw1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

submit_url_batch

Submit multiple URLs to Bing Webmaster Tools for indexing to improve search visibility and ensure content is discoverable.

Instructions

Submit multiple URLs for indexing.

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

Input Schema

NameRequiredDescriptionDefault
site_urlYes
urlsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Submit for indexing' implies a write operation, but the description doesn't disclose rate limits, authentication requirements, whether this is asynchronous, what happens on success/failure, or how it differs from similar tools. This leaves significant gaps for an agent to understand the tool's behavior.

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?

The description is extremely concise - a single sentence that directly states the tool's purpose. There's zero wasted language or unnecessary elaboration, making it easy to parse and understand at a glance.

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 tool with 2 required parameters, 0% schema description coverage, no annotations, and multiple similar sibling tools, the description is insufficient. While an output schema exists (which helps with return values), the description doesn't address when to use batch versus individual submission, parameter meanings, or behavioral aspects like rate limits or asynchronous processing.

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 for both parameters, the description provides no information about what 'site_url' and 'urls' represent, their format requirements, or their relationship. The description mentions 'multiple URLs' which hints at the 'urls' array parameter, but doesn't explain the purpose of 'site_url' or provide any parameter semantics beyond what's obvious from the parameter names.

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 the action ('submit') and resource ('multiple URLs for indexing'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'submit_url' (singular) or 'submit_content', leaving some ambiguity about when to use this batch version versus alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives like 'submit_url' (for single URLs) or 'submit_content'. There's no mention of prerequisites, constraints, or typical use cases for batch submission versus individual submissions.

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