Skip to main content
Glama

bing_get_url_info

Check a specific URL's Bing index status and crawl information to diagnose indexing issues and verify whether Bing has discovered or crawled the page.

Instructions

Get index status and crawl information for a specific URL from Bing.

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_get_url_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe specific URL to check
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden, yet it only describes the subject matter. It says nothing about whether the target site must be verified in Bing Webmaster Tools, whether the URL must belong to siteUrl, what happens for unindexed URLs, rate limits, or what the response contains. 'Get' implies read-only but that is inference, not disclosure.

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?

A single front-loaded sentence with zero filler; the resource and scope come first. Its brevity is efficient rather than padded, though it is short enough that useful qualifiers were omitted rather than compressed.

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?

With no annotations, no output schema, and two required parameters whose relationship is unstated, the description is too thin for the tool's complexity. An agent still lacks the prerequisites (site verification), the siteUrl/url dependency, and any sense of the returned data beyond the phrase 'index status and crawl information'.

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 coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds no meaning beyond the schema — notably it does nothing to clarify the relationship between the vague 'siteUrl' ('The site URL') and 'url', such as whether siteUrl is the verified property the URL must fall under.

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 ('Get') and a specific resource ('index status and crawl information') scoped to 'a specific URL from Bing', so the agent knows exactly what the tool returns. It never distinguishes itself from near-neighbors like bing_get_page_stats or bing_get_crawl_issues, which read on similar data, so sibling differentiation is left to guesswork.

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?

There is no when-to-use guidance, no when-not-to-use guidance, and no alternative tool named. An agent can only infer from the resource noun that this is for per-URL inspection, and must guess how it differs from the page-statistics and crawl-issue siblings.

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