Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

remove_country_region_settings

Remove country or region targeting settings from a specific website in Bing Webmaster Tools to adjust geographic search visibility.

Instructions

Remove country/region settings from a specific site.

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

Raises: BingWebmasterError: If settings cannot be removed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
settingsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Generic handler wrapper function created for each tool, including remove_country_region_settings. Executes the tool by dynamically retrieving and calling the underlying RegionalSettingsService.remove_country_region_settings method via getattr.
    @mcp.tool()
    @wraps(original_method)
    async def wrapper(*args: Any, **kwargs: Any) -> Any:
        # Filter out any 'self' arguments that might be passed by the MCP client
        kwargs = {k: v for k, v in kwargs.items() if k != "self"}
    
        async with service as s:
            service_obj = getattr(s, service_attr)
            # Get the method from the instance
            method = getattr(service_obj, method_name)
            # Call the method directly - it's already bound to the instance
            return await method(*args, **kwargs)
  • Registers the remove_country_region_settings tool by calling wrap_service_method, which decorates the handler with @mcp.tool().
    remove_country_region_settings = wrap_service_method(  # noqa: F841
        mcp, service, "regional", "remove_country_region_settings"
    )
  • Top-level call to add_bing_webmaster_tools, which registers all Bing Webmaster tools including remove_country_region_settings.
    add_bing_webmaster_tools(mcp, bing_service)
  • Helper that generates the MCP tool handler for service methods, used for remove_country_region_settings.
    def wrap_service_method(
        mcp: FastMCP, service: BingWebmasterService, service_attr: str, method_name: str
    ) -> Callable[..., Any]:
        """Helper function to wrap a service method with mcp.tool() while preserving its signature and docstring.
    
        Args:
            mcp: The MCP server instance
            service: The BingWebmasterService instance
            service_attr: The service attribute name (e.g., 'sites', 'submission')
            method_name: The method name to wrap
    
        Returns:
            The wrapped method as an MCP tool
        """
        # Get the service class from our mapping
        service_class = SERVICE_CLASSES[service_attr]
        # Get the original method
        original_method = getattr(service_class, method_name)
        # Get the signature
        sig = inspect.signature(original_method)
        # Remove 'self' parameter from signature
        parameters = list(sig.parameters.values())[1:]  # Skip 'self'
    
        # Create new signature without 'self'
        new_sig = sig.replace(parameters=parameters)
    
        # Create wrapper function with same signature
        @mcp.tool()
        @wraps(original_method)
        async def wrapper(*args: Any, **kwargs: Any) -> Any:
            # Filter out any 'self' arguments that might be passed by the MCP client
            kwargs = {k: v for k, v in kwargs.items() if k != "self"}
    
            async with service as s:
                service_obj = getattr(s, service_attr)
                # Get the method from the instance
                method = getattr(service_obj, method_name)
                # Call the method directly - it's already bound to the instance
                return await method(*args, **kwargs)
    
        # Copy signature and docstring
        wrapper.__signature__ = new_sig  # type: ignore
        wrapper.__doc__ = original_method.__doc__
    
        return wrapper
  • Initializes the 'regional' service attribute on BingWebmasterService, which provides the remove_country_region_settings method.
    self.regional = regional_settings.RegionalSettingsService(self.client)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that settings 'cannot be removed' might raise an error, but doesn't specify what 'remove' entails (e.g., permanent deletion, reversible change, impact on site functionality). For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps about side effects and constraints.

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 efficiently structured with a clear purpose statement followed by Args and Raises sections. However, the Args section is under-specified (just parameter names), and the overall content is somewhat sparse for a tool with 3 parameters and no annotations.

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?

For a mutation tool with 3 parameters, 0% schema coverage, no annotations, and sibling tools that include both 'add_country_region_settings' and 'get_country_region_settings', the description is incomplete. It doesn't explain the relationship between add/remove/get operations, doesn't describe the settings structure, and while an output schema exists, the description provides minimal context about the removal operation's effects.

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 parameters are undocumented in the schema. The description only lists parameter names ('site_url', 'settings') without explaining what they represent, their formats, or valid values. It doesn't compensate for the schema gap, leaving the agent with insufficient information to construct valid inputs.

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 clearly states the action ('Remove') and resource ('country/region settings from a specific site'), making the purpose understandable. It distinguishes from siblings like 'add_country_region_settings' by specifying removal, but doesn't explicitly contrast with other removal tools like 'remove_blocked_url' or 'remove_site'.

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. While the name implies it's for removing country/region settings, there's no mention of prerequisites, when removal is appropriate, or what happens after removal. The description doesn't help the agent decide between this and other site configuration tools.

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