Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_link_counts

Retrieve the total number of links pointing to your site, organized by source. Specify a site URL and page number to get paginated link counts, helping you analyze your backlink profile.

Instructions

Retrieve link counts for a specific site.

Args: site_url: The URL of the site page: The page number of results to retrieve

Returns: LinkCounts: Summary of link counts

Raises: BingWebmasterError: If link counts cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
LinksYes
TotalPagesYes

Implementation Reference

  • Tool 'get_link_counts' is registered using wrap_service_method, wrapping the 'get_link_counts' method on link_analysis.LinkAnalysisService (the 'links' service attribute). The actual handler is the method 'get_link_counts' in the external package 'bing_webmaster_tools.services.link_analysis.LinkAnalysisService'.
    get_link_counts = wrap_service_method(mcp, service, "links", "get_link_counts")  # noqa: F841
  • The wrap_service_method helper dynamically wraps any service method as an MCP tool by capturing its signature, docstring, and creating an async wrapper that calls the service method via the BingWebmasterService context manager.
    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
Behavior2/5

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

No annotations are present, so the description carries full burden. It implies a read-only operation ('retrieve') but does not explicitly state no side effects, rate limits, or other behavioral traits. Minimal disclosure beyond the basic function.

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 relatively short and front-loaded with the main sentence. It uses a clear structure with Args/Returns/Raises. There is no wasted text, though it could be more concise by omitting obvious formatting.

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?

The tool has an output schema, so detailed return values are not required, but the description omits explanation of pagination (via page parameter) and the meaning of the required 'self' parameter. The overall context is incomplete for a paginated tool with an undocumented parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description adds meaning for site_url and page parameters. However, the required 'self' parameter is not described, leaving a gap. The added descriptions are basic but functional.

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 retrieves link counts for a specific site, using a specific verb and resource. It distinguishes from siblings like get_url_links which deals with actual links, not counts. However, it does not explicitly differentiate from similar tools.

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 includes Args/Returns/Raises which aid usage but lacks contextual recommendations or prerequisites.

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