Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

remove_site_role

Remove a user's access role from a specific site in Bing Webmaster Tools to manage permissions and control site administration.

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

  • Core handler logic for the 'remove_site_role' tool (shared across tools). Decorated with @mcp.tool(), it wraps and executes the underlying service method 'remove_site_role' from SiteManagementService.
    @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
  • Specific registration of the 'remove_site_role' MCP tool by invoking the wrapper with the 'sites' service and 'remove_site_role' method.
    remove_site_role = wrap_service_method(mcp, service, "sites", "remove_site_role")  # noqa: F841
  • Helper function that creates and registers the tool handler, preserving signature and docstring from the original service method.
    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
  • Invocation of the function that registers all Bing Webmaster tools, including 'remove_site_role'.
    add_bing_webmaster_tools(mcp, bing_service)
  • Instantiation of the 'sites' service (SiteManagementService) used by the 'remove_site_role' tool.
    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. It states the tool removes access (implying a destructive mutation) but doesn't disclose behavioral traits like required permissions, whether the action is reversible, rate limits, or what happens on success. The 'Raises' section adds minimal error context but lacks operational details needed for safe invocation.

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 appropriately concise with three short sections: purpose, Args, and Raises. Each sentence earns its place, and the structure is clear. However, the Args section is under-specified rather than truly concise, as it lacks necessary details for the parameters.

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 complexity (destructive mutation, 3 parameters with 0% schema coverage, no annotations), the description is incomplete. It doesn't explain parameter usage, behavioral implications, or error handling beyond a generic exception. While an output schema exists, the description doesn't address key contextual gaps for a mutation tool with undocumented inputs.

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 lists 'site_url' and 'site_role' in the Args section but doesn't explain their semantics, formats, or examples (e.g., what a valid site_url looks like, how site_role is structured). It misses the 'self' parameter entirely, leaving it undocumented. The description adds minimal value beyond naming parameters.

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 tool's purpose: 'Remove a user's site access.' It specifies the verb ('remove') and resource ('user's site access'), making the action explicit. However, it doesn't distinguish this tool from similar siblings like 'remove_site' or 'remove_blocked_url', which also remove things but target 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., needing existing site roles), exclusions, or comparisons to siblings like 'get_site_roles' (for viewing) or 'add_site_roles' (for adding). The 'Raises' section hints at error conditions but doesn't offer usage context.

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