Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_link_counts

Retrieve link count data for websites to analyze backlink profiles and inbound connections using Bing Webmaster Tools.

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

  • Specific registration of the 'get_link_counts' MCP tool by wrapping the 'links' service method with @mcp.tool() decorator using the helper function.
    get_link_counts = wrap_service_method(mcp, service, "links", "get_link_counts")  # noqa: F841
  • Generic helper that creates the handler wrapper for each tool, registers it as @mcp.tool(), copies schema from original method signature, and executes the underlying service method in async context.
    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
  • Invokes the tool registration function, which includes the get_link_counts tool registration.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the 'links' service instance (LinkAnalysisService) as an attribute, used by the tool wrappers.
    # Expose all services directly
    self.sites = site_management.SiteManagementService(self.client)
    self.submission = submission.SubmissionService(self.client)
    self.traffic = traffic_analysis.TrafficAnalysisService(self.client)
    self.crawling = crawling.CrawlingService(self.client)
    self.keywords = keyword_analysis.KeywordAnalysisService(self.client)
    self.links = link_analysis.LinkAnalysisService(self.client)
    self.content = content_management.ContentManagementService(self.client)
    self.blocking = content_blocking.ContentBlockingService(self.client)
    self.regional = regional_settings.RegionalSettingsService(self.client)
    self.urls = url_management.UrlManagementService(self.client)
  • Maps 'links' service attribute to LinkAnalysisService class for signature introspection in wrappers.
    # Map service attribute names to their corresponding service classes
    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,
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that it 'Retrieves link counts' and raises an error if they cannot be retrieved, which implies a read-only operation, but lacks details on permissions, rate limits, pagination behavior, or what 'LinkCounts' summary entails. This is insufficient for a tool with parameters and potential complexity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with sections (Args, Returns, Raises), which aids readability, but includes redundant elements like 'Raises' that could be inferred. The core purpose is stated upfront, but the formatting adds some bulk without maximizing efficiency, making it adequate but not optimally concise.

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 the tool has an output schema (indicating returns are documented elsewhere), the description doesn't need to detail return values. However, with no annotations, 3 parameters (one undocumented in description), and potential behavioral nuances, the description provides basic purpose and error handling but lacks comprehensive context for safe and effective use.

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 for undocumented parameters. It lists 'site_url' and 'page' in the Args section, adding some meaning beyond the schema, but omits 'self' entirely and doesn't explain what 'page' refers to (e.g., pagination of results). This partial coverage leaves gaps in parameter understanding.

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 with a specific verb ('Retrieve') and resource ('link counts for a specific site'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_url_links' or 'get_children_url_info', which might also involve link-related data, so it misses full sibling differentiation.

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 mentions retrieving link counts but doesn't specify context, prerequisites, or exclusions compared to other link-related tools in the sibling list, leaving the agent without usage direction.

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