Bing Webmaster Tools MCP Server

get_country_region_settings

Retrieve the country or region settings for a specified site to view and manage geographic targeting in Bing Webmaster Tools.

Instructions

Retrieve country/region settings for a specific site.

Args: site_url: The URL of the site to get settings for

Returns: List[CountryRegionSettings]: List of country/region settings

Raises: BingWebmasterError: If settings cannot be retrieved

Input Schema

TableJSON Schema

Name	Required	Description	Default
`self`	Yes
`site_url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "CountryRegionSettings": {
+      "properties": {
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "TwoLetterIsoCountryCode": {
+          "maxLength": 2,
+          "minLength": 2,
+          "title": "Twoletterisocountrycode",
+          "type": "string"
+        },
+        "Type": {
+          "$ref": "#/$defs/CountryRegionSettingsType"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "default": "CountryRegionSettings:#Microsoft.Bing.Webmaster.Api",
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "Date",
+        "TwoLetterIsoCountryCode",
+        "Type",
+        "Url"
+      ],
+      "title": "CountryRegionSettings",
+      "type": "object"
+    },
+    "CountryRegionSettingsType": {
+      "enum": [
+        0,
+        1,
+        2,
+        3
+      ],
+      "title": "CountryRegionSettingsType",
+      "type": "integer"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/CountryRegionSettings"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_country_region_settingsOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It includes return type and error info but does not explicitly state read-only nature, side effects, or rate limits. The verb 'Retrieve' implies safety, but transparency could be improved.

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 concise with a clear one-liner purpose and structured docstring (Args, Returns, Raises). No unnecessary information, though it could be more compact.

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 is simple, and output schema exists, so return value details are partially covered. However, the description omits semantics of 'self' parameter and does not mention edge cases or behavior when settings are unavailable.

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 description coverage is 0%, so the description must compensate. It explains 'site_url' but ignores 'self' parameter entirely. Only partial compensation for one of two parameters.

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 explicitly states the verb 'Retrieve', the resource 'country/region settings', and the scope 'for a specific site', clearly distinguishing it from sibling tools like add/remove_country_region_settings.

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, no prerequisites, conditions, or exclusions. It only describes the action without context.

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

Deploy Server