Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: List Sites

bing_webmaster_list_sites
Read-only

Lists every site added to Bing Webmaster Tools for the API key, with registered URL form and verification status, plus codes for unverified sites so you can select a valid site for data calls.

Instructions

Every site the API key's user has added to Bing Webmaster Tools, in its registered form (scheme and trailing slash as Bing stores them), with whether it is verified. Unverified sites carry their verification codes. Every other tool takes one of these as site; data calls on an unverified site fail with NotAuthorized.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bing_webmaster_list_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum sites to return (1-1000). Defaults to 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it read-only and open-world, but the description adds important behavior beyond that: returned sites are in Bing's registered form, verified status is included, unverified sites expose verification codes, and downstream data calls fail with NotAuthorized on unverified sites.

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?

Two dense sentences with no wasted wording. The returned data shape is front-loaded, followed immediately by the downstream dependency and authorization caveat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with no output schema, the description explains what is returned, how site values are formatted, verification status, and the consequence of using unverified sites. No essential information for correct invocation is missing.

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?

The schema has 100% description coverage for the single `limit` parameter, so it already explains the 1-1000 range and default of 100. The description adds no additional meaning about how limiting affects results, 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: lists every site the API key's user has added to Bing Webmaster Tools. It also specifies the exact returned form (registered scheme and trailing slash) and includes verification status and verification codes, making the tool clearly distinguishable from sibling data-fetching tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states that every other tool takes one of these site values as `site`, which tells the agent this is the identifier-discovery step before data calls. It also warns that data calls on unverified sites fail with NotAuthorized, giving a clear operational constraint.

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