Skip to main content
Glama

bing_list_sites

Retrieve all sites verified in Bing Webmaster Tools for the current API key, so you can identify available properties before submitting URLs or reviewing reports.

Instructions

List all sites verified in Bing Webmaster Tools for the current API key

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose a meaningful constraint — results are limited to sites verified under the current API key, so this is not a cross-account listing — and 'List' implies a read-only operation. It says nothing about ordering, pagination, or empty-result behavior, which is a real gap for a zero-parameter listing tool.

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?

A single twelve-word sentence with no filler, and the scoping constraint ('current API key') is placed where it is immediately visible. Nothing is padded or restated from the name.

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 trivial no-parameter listing call the description is close to sufficient, but with no output schema and no annotations the agent gets no indication of what a 'site' record contains or whether the list can be large. A short note on the returned fields would close the remaining gap.

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, so there is nothing for the description to disambiguate; the baseline of 4 applies. The mention of 'current API key' usefully clarifies that the credential, not a parameter, determines scope.

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 ('List') and a specific resource ('sites verified in Bing Webmaster Tools'), plus a scope qualifier ('for the current API key'). An agent can distinguish this from bing_list_sitemaps or the bing_get_* stat tools by the noun 'sites' alone, but the description never explicitly contrasts itself with those siblings.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage is only implied by the object of the verb: an agent calls this when it needs the inventory of verified sites, which is a reasonably self-evident discovery operation.

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