Skip to main content
Glama
Sign In
Bing Webmaster Tools MCP

Bing Webmaster Tools MCP

by rafavillaplana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

URL index status

get_url_info
Read-only

Retrieve Bing Webmaster Tools index details for one URL, including HTTP status, crawl dates, size, and document links to diagnose indexing issues.

Instructions

Index information for one URL: HTTP status, discovery and last crawl dates, size, document links…

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": "get_url_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL
siteUrlYesSite URL exactly as verified in Bing Webmaster Tools (e.g. https://example.com/). Call list_sites if unsure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description usefully adds the kinds of values returned, which matters because there is no output schema, but it omits behavior for unindexed URLs, errors, and any rate limits.

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 keeps it tight, and the enumerated fields are efficient. The trailing ellipsis is a minor structural weakness that makes the return list feel incomplete.

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?

Required parameters and safety semantics are adequately covered via schema and annotations. However, with no output schema, the description's partial field list ending in '…' leaves the full return shape and non-happy-path behavior under-specified.

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 the schema itself explains that siteUrl must exactly match the verified Bing Webmaster Tools site and suggests list_sites when unsure. The description adds no parameter-level meaning beyond that, so the baseline of 3 is appropriate.

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: index information for one URL, and lists several returned fields (HTTP status, discovery/last crawl dates, size, document links). It does not explicitly distinguish itself from siblings such as get_url_traffic_info or get_inbound_links, so it falls short of a 5.

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 gives no when-to-use or when-not-to-use guidance and does not name alternatives. 'For one URL' implies scope but does not tell the agent which sibling to choose for traffic, links, or keyword data. The list_sites hint lives in the schema, not the description, so it does not count here.

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