Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

add_country_region_settings

Set country/region targeting for a site in Bing Webmaster Tools to define its geographic market and improve search relevance.

Instructions

Add country/region settings for a specific site.

Args: site_url: The URL of the site settings: The country/region settings to add

Raises: BingWebmasterError: If settings cannot be added

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
settingsYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • removedInput schema / properties / self
      Removed value: -{
-  "title": "self",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "self",
-  "site_url",
-  "settings"
-]New value: +[
+  "site_url",
+  "settings"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "null"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "add_country_region_settingsOutput",
+  "type": "object"
+}
  3. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses that it raises BingWebmasterError on failure (useful), but does not mention potential side effects, idempotency, whether it overwrites existing settings, or required permissions. As an add operation, the mutating nature is inferred but not explicitly stated, and no response format is described despite having an output schema.

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 compact: a one-line purpose and a short Args section. Each sentence earns its place; no fluff. However, it could be improved by adding brief value mentions of key fields, but it's not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (nested settings object, required fields, enum), the description is under-specified. No example, no return value explanation (though output schema exists, the description doesn't confirm what to expect), no error handling details beyond naming the error type. For a mutating operation with no annotations, more context is needed for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description only repeats parameter names: 'site_url: The URL of the site' and 'settings: The country/region settings to add'. This adds no meaning beyond the schema's parameter titles. The nested CountryRegionSettings object is not explained; the agent must infer its required fields from the schema, which does provide them, but the description doesn't help interpret the enum values of 'Type' or the meaning of 'TwoLetterIsoCountryCode'.

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 ('Add') and resource ('country/region settings') for a specific site. Distinguishes from siblings like get_country_region_settings and remove_country_region_settings by naming the operation explicitly, though it doesn't name them.

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 on when to use this tool versus alternatives. It doesn't mention that get_country_region_settings is for retrieval or remove_country_region_settings for deletion, nor does it specify prerequisites like verifying site ownership first. The description implies usage via 'Add' but doesn't provide context.

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