Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_deep_link

Retrieve deep links for a specific URL from Bing Webmaster Tools to analyze internal linking structure and improve site navigation.

Instructions

Get deep links for a specific algo URL. (Deprecated)

Args: site_url: The URL of the site url: The specific URL to get deep links for

Returns: List[DeepLink]: List of deep links

Raises: BingWebmasterError: If deep links cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the MCP tool 'get_deep_link' by wrapping the link_analysis.LinkAnalysisService.get_deep_link method using wrap_service_method.
    get_deep_link = wrap_service_method(mcp, service, "links", "get_deep_link")  # noqa: F841
  • The wrap_service_method helper creates the actual handler function for the tool, decorating it with @mcp.tool(), preserving signature/docstring, and delegating execution to the underlying service.links.get_deep_link 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
  • Top-level registration call that triggers addition of all tools including 'get_deep_link'.
    add_bing_webmaster_tools(mcp, bing_service)
  • BingWebmasterService.__aenter__ initializes the 'links' service attribute used by the get_deep_link tool wrapper.
    self.links = link_analysis.LinkAnalysisService(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 full burden. It mentions potential errors ('Raises: BingWebmasterError') which is helpful, but doesn't disclose other behavioral traits like whether this is a read-only operation, rate limits, authentication needs, or what happens when deep links cannot be retrieved beyond the error.

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 sized with clear sections (Args, Returns, Raises) and front-loaded purpose statement. The deprecation warning is efficiently placed. However, the 'self' parameter documentation is confusing and could be more clearly explained.

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?

The tool has an output schema (List[DeepLink]), so the description doesn't need to explain return values. However, for a deprecated tool with 3 undocumented parameters and no annotations, the description should provide more context about why it's deprecated, migration paths, and clearer parameter guidance. The error information is helpful but insufficient.

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 compensate. It lists parameters in the Args section with brief labels but provides minimal semantic context. The description doesn't explain what 'self' parameter means, how 'site_url' differs from 'url', or what format these URLs should have. The parameter documentation is insufficient given the complete lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get deep links for a specific algo URL' which provides a verb ('Get') and resource ('deep links'), but it's vague about what 'algo URL' means and doesn't distinguish from sibling tools like 'get_deep_link_algo_urls' or 'get_deep_link_blocks'. The deprecation warning adds context but doesn't clarify the specific purpose.

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 on when to use this tool versus alternatives like 'get_deep_link_algo_urls' or 'get_deep_link_blocks'. The deprecation warning implies it should be avoided, but doesn't specify what to use instead or when it might still be appropriate.

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