Bing Webmaster Tools MCP Server

get_site_moves

Retrieve site move settings for a specific site URL to check redirects or change-of-address status in Bing Webmaster Tools.

Instructions

Get site move information for a specific site.

Args: site_url: The URL of the site

Returns: List[SiteMoveSettings]: List of site move settings

Raises: BingWebmasterError: If the site move information cannot be retrieved

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.

Input Schema

TableJSON Schema

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

Output Schema

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

changedInput schema / required

Previous value: -[
-  "self",
-  "site_url"
-]New value: +[
+  "site_url"
+]

Changed1 schema field changedv1.0.0Jan 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "SiteMoveScope": {
+      "enum": [
+        0,
+        1,
+        2
+      ],
+      "title": "SiteMoveScope",
+      "type": "integer"
+    },
+    "SiteMoveSettings": {
+      "properties": {
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "MoveScope": {
+          "$ref": "#/$defs/SiteMoveScope"
+        },
+        "MoveType": {
+          "$ref": "#/$defs/SiteMoveType"
+        },
+        "SourceUrl": {
+          "pattern": "^https?://",
+          "title": "Sourceurl",
+          "type": "string"
+        },
+        "TargetUrl": {
+          "pattern": "^https?://",
+          "title": "Targeturl",
+          "type": "string"
+        },
+        "__type": {
+          "default": "SiteMoveSettings:#Microsoft.Bing.Webmaster.Api",
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "Date",
+        "MoveScope",
+        "MoveType",
+        "SourceUrl",
+        "TargetUrl"
+      ],
+      "title": "SiteMoveSettings",
+      "type": "object"
+    },
+    "SiteMoveType": {
+      "enum": [
+        0,
+        1
+      ],
+      "title": "SiteMoveType",
+      "type": "integer"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/SiteMoveSettings"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_site_movesOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

B3.2/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the return type (List[SiteMoveSettings]), the error raised (BingWebmasterError), and pagination semantics (next_offset to continue), which is solid for a retrieval tool. However, it never explicitly states this is a read-only, non-destructive operation, and provides no detail about what a 'site move' entails or behavior on invalid site_url.

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?

The text is compact and front-loaded: purpose first, then Args/Returns/Raises, with the high-value pagination note last. Every sentence earns its place with little waste. The Docstring-style Args/Returns sections are slightly verbose but defensible. It is efficient without being under-specified.

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 low-complexity read tool with an output schema and moderate schema coverage, the description is nearly complete: it covers purpose, the required parameter, return type, error type, and pagination. The main missing piece is usage guidance relative to siblings and an explicit statement of read-only behavior, but nothing an agent needs to invoke the call correctly is absent.

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 coverage is 67% (limit and offset are described in the schema; site_url is not). The description adds minimal meaning for site_url ('The URL of the site') and, more valuably, explains the limit/offset relationship via next_offset — genuinely beyond the schema's standalone param descriptions. Since coverage is moderate, the description compensates reasonably but does not fully document site_url semantics.

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?

The description states a specific verb ('Get') plus a resource ('site move information') and a clear scope ('for a specific site' via site_url). This is unambiguous and distinct from the actual write counterpart among siblings (submit_site_move). However, it does not explicitly name or disambiguate against siblings such as get_sites or submit_site_move, so it stops short of the top tier.

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?

There is no guidance on when to use this tool versus alternatives. It never distinguishes itself from get_sites, submit_site_move, or other retrieval tools, and offers no exclusions or conditions. The pagination note is operational behavior, not usage-vs-alternative direction, so an agent gets no help choosing this over a sibling.

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

Deploy Server