Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_country_region_settings

Retrieve country/region settings for a site to identify and verify its geographic targeting.

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

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
NameRequiredDescriptionDefault
limitNoMaximum number of rows to return.
offsetNoIndex of the first row.
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • 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"
+]
  2. Changed1 schema field changedv1.0.0
    • 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"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it performs well: it documents pagination mechanics (next_offset, offset-based continuation), default/max limits, the returned type, and raises BingWebmasterError on failure. It stops short of disclosing auth requirements or what specific setting fields are returned, but coverage is strong.

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?

Organized docstring with Args/Returns/Raises sections plus a focused pagination note. Each line earns its place and the most behaviorally important constraint (limit/pagination) is front-loaded. Slightly verbose only in restating site_url in Args.

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?

Complete for a list-retrieval tool: output schema exists (List[CountryRegionSettings]), error behavior is stated, and pagination instructions are explicit. The only minor gap is not describing what fields each CountryRegionSettings entry contains, which the output schema likely handles.

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 67%, and the description compensates by explaining the pagination contract referencing limit and offset explicitly, including defaults (50) and cap (500). site_url is only restated as 'URL of the site', but the pagination detail adds real meaning beyond the bare schema.

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 ('Retrieve') and resource ('country/region settings for a specific site'), clearly distinguishing it from the add_ and remove_ sibling variants. The purpose is unambiguous, though it doesn't explicitly name its siblings like some top-tier descriptions do.

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?

Gives context that it operates 'for a specific site' and implies a read-only contrast to the add/remove counterparts in the sibling list, but never explicitly states when to use this tool versus add_country_region_settings or remove_country_region_settings. No exclusions or alternative routing is provided.

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

Deploy Server

Other Tools