Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_site_moves

Retrieve site move settings for a specific site URL, providing migration details and configuration information to manage site transitions within 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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.0.0
    • 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"
+}
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description mentions that the tool returns a list of SiteMoveSettings and can raise BingWebmasterError, adding some behavioral context. However, without annotations, it lacks details on permissions, rate limits, or side effects. The read-only nature is implied but not explicitly stated.

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 description is fairly concise, using a structured docstring format with Args, Returns, Raises sections. The first sentence captures the purpose, but the structure is somewhat verbose for a simple tool.

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?

The tool has 2 parameters and an output schema exists, so the description need not detail return values. However, the missing explanation for the 'self' parameter and lack of usage context leave gaps. It is adequate but not complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only explains 'site_url' as 'The URL of the site' – minimal value beyond the parameter name. The 'self' parameter is not described at all, leaving the user guessing its purpose.

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 description clearly states the action ('Get'), the resource ('site move information'), and the scope ('for a specific site'). This distinguishes it from sibling tools like 'submit_site_move' which handle submission.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention that this should be used after submitting a site move, or that it's complementary to 'submit_site_move'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zizzfizzix/mcp-server-bwt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server