Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

remove_site

Remove a site from Bing Webmaster Tools to stop tracking and management of that URL in your account.

Instructions

Remove a site from Bing Webmaster Tools.

Args: site_url: The URL of the site to remove

Raises: BingWebmasterError: If the site cannot be removed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler logic for the 'remove_site' tool (shared with all tools): wraps and executes the underlying SiteManagementService.remove_site method via the BingWebmasterService instance.
    # 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__
  • Dynamically extracts and adapts the input schema from the original service method signature for the MCP tool.
    # 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)
  • Registers the 'remove_site' tool on the MCP server instance.
    remove_site = wrap_service_method(mcp, service, "sites", "remove_site")  # noqa: F841
  • Mapping of service attributes like 'sites' to their classes, used for method resolution and schema extraction.
    SERVICE_CLASSES = {
        "sites": site_management.SiteManagementService,
        "submission": submission.SubmissionService,
        "traffic": traffic_analysis.TrafficAnalysisService,
        "crawling": crawling.CrawlingService,
        "keywords": keyword_analysis.KeywordAnalysisService,
        "links": link_analysis.LinkAnalysisService,
        "content": content_management.ContentManagementService,
        "blocking": content_blocking.ContentBlockingService,
        "regional": regional_settings.RegionalSettingsService,
        "urls": url_management.UrlManagementService,
    }
  • Instantiates the SiteManagementService (containing remove_site) as self.sites for use by tool wrappers.
    self.sites = site_management.SiteManagementService(self.client)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool removes a site, implying a destructive mutation, but doesn't specify whether this is reversible, what permissions are required, or what happens to associated data (e.g., crawl stats, settings). The 'Raises' section mentions an error condition, which adds some context, but overall behavioral details are sparse for a destructive operation.

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 well-structured with clear sections (main description, Args, Raises) and uses minimal words to convey the core functionality. Every sentence adds value: the first states the purpose, the second explains the key parameter, and the third notes error conditions. However, the missing explanation for the 'self' parameter slightly reduces efficiency.

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?

Given that this is a destructive mutation tool with no annotations, 0% schema coverage, and an output schema exists (which may cover return values), the description is moderately complete. It covers the basic purpose and one parameter but lacks details on the second parameter, behavioral implications, and usage context. The output schema might help, but the description itself has notable gaps for a tool that permanently removes resources.

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 the schema provides no parameter documentation. The description explicitly documents 'site_url' with a brief explanation, but it doesn't mention the 'self' parameter at all. With 2 parameters total and only 1 documented in the description, this leaves significant gaps in understanding what 'self' represents or how to use it.

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 ('a site from Bing Webmaster Tools'), making the purpose unambiguous. It distinguishes this as a deletion operation rather than a read or update. However, it doesn't explicitly differentiate from sibling tools like 'remove_blocked_url' or 'remove_site_role', which also perform removal operations on different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the site must exist in Bing Webmaster Tools), nor does it compare with related tools like 'get_sites' (to list sites first) or 'add_site' (for adding sites). The only implicit context is that it's for site management, but no explicit usage instructions are given.

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