Skip to main content
Glama
isiahw1

mcp-server-bing-webmaster

remove_country_region_settings

Remove country or region targeting settings from a website in Bing Webmaster Tools to disable geographic content restrictions.

Instructions

Remove country/region targeting settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYes
country_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the MCP tool named 'remove_country_region_settings' with its description.
    @mcp.tool(
        name="remove_country_region_settings",
        description="Remove country/region targeting settings.",
    )
  • The main handler function that executes the tool by calling the Bing Webmaster API's RemoveCountryRegionSettings endpoint.
    async def remove_country_region_settings(
        site_url: Annotated[str, "The URL of the site"],
        country_code: Annotated[str, "ISO country code to remove"],
    ) -> Dict[str, str]:
        """
        Remove country/region targeting settings.
    
        Args:
            site_url: The URL of the site
            country_code: ISO country code to remove
    
        Returns:
            Success message
        """
        async with api:
            await api._make_request(
                "RemoveCountryRegionSettings",
                "POST",
                {"siteUrl": site_url, "countryCode": country_code},
            )
            return {"message": f"Country settings for {country_code} removed successfully"}
Behavior2/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. It states a removal action, implying mutation, but lacks details on permissions, reversibility, side effects, or response format. This is inadequate for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 a mutation tool with no annotations, 0% schema coverage, and an output schema (which helps but isn't described), the description is incomplete. It lacks behavioral context, parameter details, and usage guidance, making it insufficient for safe and effective tool invocation.

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 'site_url' and 'country_code' are undocumented in the schema. The description adds no meaning beyond the tool name, failing to explain what these parameters represent, their formats, or constraints, leaving significant gaps.

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 target ('country/region targeting settings'), providing a specific verb+resource combination. It distinguishes from siblings like 'add_country_region_settings' by indicating the opposite operation, though it doesn't explicitly contrast with other removal tools like 'remove_blocked_url'.

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. The description doesn't mention prerequisites, context, or exclusions, nor does it reference sibling tools like 'get_country_region_settings' for checking settings before removal or 'add_country_region_settings' for reversal.

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/isiahw1/mcp-server-bing-webmaster'

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