Skip to main content
Glama

bing_submit_url

Submit a single URL to Bing for indexing when IndexNow is unavailable, providing a fallback method to request search engine indexing.

Instructions

Submit a single URL to Bing for indexing. 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>",
      "url": "<url>"
    },
    "name": "bing_submit_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to submit for indexing
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 behavioral burden, and it says nothing about quota consumption, auth requirements (verified site ownership), wait time before indexing, or whether resubmitting the same URL is idempotent. The only behavioral hint is the fallback ordering, which is thin for a mutation tool with a quota sibling (bing_get_url_submission_quota) sitting next to it.

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?

Two short sentences, action first and routing second, with no wasted wording. It is well front-loaded, though it is minimal enough that it leaves gaps rather than filling them.

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?

For a simple two-parameter submission tool with no output schema, the description covers what it does and which alternative to prefer. It is still missing what a caller needs to know about success/failure feedback and quota implications, which matters for a write operation.

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%, so both parameters are documented in the schema and the baseline is 3. The description adds nothing about the distinction between siteUrl (the verified property) and url (the page to submit), which is the one ambiguity a caller could stumble on.

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?

States a specific verb and resource ("Submit a single URL to Bing for indexing") and the word "single" implicitly separates it from the batch sibling. It does not explicitly name indexnow_submit_url, but the IndexNow reference points at the right alternative family.

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?

Gives a clear selection rule: use IndexNow as the primary method, this tool only as a fallback. That is a usable when-to-use condition, though it doesn't spell out the failure case that triggers fallback (e.g. IndexNow key not configured).

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