Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

remove_site_role

Remove a user's role and access to a site in Bing Webmaster Tools by specifying the site URL and role.

Instructions

Remove a user's site access.

Args: site_url: The URL of the site site_role: The site role to remove

Raises: BingWebmasterError: If the role cannot be removed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
site_roleYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler for 'remove_site_role' — a dynamically generated async wrapper that calls the 'remove_site_role' method on the 'sites' service (SiteManagementService) via the wrap_service_method helper.
    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)
  • Registration of the 'remove_site_role' tool. This line creates the tool by calling wrap_service_method, which applies @mcp.tool() to the wrapper function.
    remove_site_role = wrap_service_method(mcp, service, "sites", "remove_site_role")  # noqa: F841
  • The wrap_service_method helper that dynamically generates the MCP tool. It introspects SiteManagementService.remove_site_role, builds a signature, and decorates an async wrapper with @mcp.tool().
    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
  • Maps the 'sites' service attribute to SiteManagementService, which contains the remove_site_role method used by the tool.
    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,
    }
  • Top-level entry point where add_bing_webmaster_tools is called, which registers all tools including remove_site_role on the MCP server.
    # Add the tools to the MCP server
    add_bing_webmaster_tools(mcp, bing_service)
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states the action and an error condition, lacking details on destructiveness, side effects, permissions, or response behavior.

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 very short and to the point, with a single line and list of args. It is efficient, though it sacrifices informational depth for brevity.

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 required parameters and no annotations, the description is incomplete: it does not explain the 'self' parameter, lacks return value details despite an output schema, and omits prerequisites or context about role removal.

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 description must clarify parameter meaning. It merely restates parameter names with trivial descriptions (e.g., 'The URL of the site'), adding no value over the schema; the complex site_role type is not explained.

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 states 'Remove a user's site access,' which is a clear verb+resource. It distinguishes from sibling tools like add_site_roles and get_site_roles, though it could be more precise by mentioning 'role' removal.

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 such as add_site_roles or other role-related tools, and no conditions or prerequisites are mentioned.

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