Skip to main content
Glama
Sign In
Bing Webmaster Tools MCP

Bing Webmaster Tools MCP

by rafavillaplana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List sites

list_sites
Read-only

Retrieve your sites in Bing Webmaster Tools and check whether each is verified. Call this first to get the exact site URL for further queries.

Instructions

Lists the user's sites in Bing Webmaster Tools and whether each is verified. Call this first to get the exact siteUrl.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.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, so the safety profile is covered. The description adds that results carry a verification flag and that this call is a prerequisite for others, but says nothing about auth scope, pagination, or result shape.

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 short sentences, purpose first and the sequencing instruction second. Every clause earns its place with no redundancy.

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

Completeness4/5

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

For a no-param read tool with no output schema, the description covers what is listed, the extra verification field, and why the agent should call it early. It stops short of describing the remaining returned fields or volume, which is a minor gap given the trivial interface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is trivially empty at 100% coverage, so there is no parameter semantics to add. Baseline 4 applies.

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 the user's sites in Bing Webmaster Tools') plus a distinguishing detail (verified status), and frames itself as the entry point that yields the siteUrl every other tool needs, which separates it from siblings like get_sitemaps or get_url_info.

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?

'Call this first to get the exact siteUrl' gives explicit ordering guidance relative to the other 15 tools in the family. It doesn't state a when-not condition, but for a zero-argument enumeration call there is little to exclude.

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