Bing Webmaster Tools MCP Server

get_sites

Retrieve all sites from your Bing Webmaster Tools account, with pagination to handle large lists.

Instructions

Retrieve all sites in the user's Bing Webmaster Tools account.

Returns: List[Site]: List of sites associated with the account

Raises: BingWebmasterError: If the API request fails

Returns at most limit rows (default 50, max 500). When the result reports a next_offset, call again with offset=next_offset to get more rows.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of rows to return.
`offset`	No	Index of the first row.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.0Sep 26, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 50,
+  "description": "Maximum number of rows to return.",
+  "maximum": 500,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Index of the first row.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}

removedInput schema / properties / self

Removed value: -{
-  "title": "self",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "self"
-]
```

Changed1 schema field changedv1.0.0Jan 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "Site": {
+      "properties": {
+        "AuthenticationCode": {
+          "title": "Authenticationcode",
+          "type": "string"
+        },
+        "DnsVerificationCode": {
+          "title": "Dnsverificationcode",
+          "type": "string"
+        },
+        "IsVerified": {
+          "title": "Isverified",
+          "type": "boolean"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "AuthenticationCode",
+        "DnsVerificationCode",
+        "IsVerified",
+        "Url"
+      ],
+      "title": "Site",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/Site"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_sitesOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

A4.7/5.0

Behavior5/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. It discloses pagination limits (default 50, max 500), the next_offset continuation pattern, and the error type raised on API failure. This gives an agent a clear contract for iterating over the full site list.

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?

The description is compact and front-loaded: purpose first, then return/error behavior, then pagination. Every sentence earns its place and there is no redundant repetition of schema details.

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?

With an output schema, error behavior, and pagination details provided, the description is complete for this tool. The only non-obvious operational detail, the next_offset loop, is explicitly explained.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the pagination protocol: 'call again with offset=next_offset to get more rows', which goes beyond the schema's basic descriptions of 'limit' and 'offset'.

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?

The opening line 'Retrieve all sites in the user's Bing Webmaster Tools account' names a specific verb and resource and defines the account scope. This is distinct from sibling tools like add_site, remove_site, and get_site_roles, none of which list all sites.

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?

The description gives clear context: use this tool to retrieve all sites in the account, with explicit pagination guidance for getting more rows. It does not explicitly name alternatives or state when not to use it, but no sibling directly competes with this listing operation.

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

Deploy Server