Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_sites

Retrieve all websites registered in your Bing Webmaster Tools account to manage site verification, indexing, and performance analysis.

Instructions

Retrieve all sites in the user's Bing Webmaster Tools account.

Returns: List[Site]: List of sites associated with the account

Raises: BingWebmasterError: If the API request fails

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler logic for the get_sites tool (shared template). Creates an MCP tool-wrapped async function that executes the underlying SiteManagementService.get_sites method within the BingWebmasterService context manager.
    @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
  • Registers the 'get_sites' tool by invoking wrap_service_method to create and decorate the handler function.
    get_sites = wrap_service_method(mcp, service, "sites", "get_sites")  # noqa: F841
  • Entry point registration: calls the function that registers all Bing Webmaster tools, including get_sites.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the 'sites' sub-service instance (SiteManagementService) used by the get_sites tool handler.
    self.sites = site_management.SiteManagementService(self.client)
  • SERVICE_CLASSES mapping used by wrap_service_method to get the original method signature and docstring for get_sites from SiteManagementService.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that it 'Retrieve[s] all sites' and includes error handling ('Raises: BingWebmasterError'), which adds some context. However, it doesn't describe critical behaviors like authentication requirements, rate limits, pagination, or whether the operation is idempotent. For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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

Conciseness5/5

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

The description is well-structured and concise, with zero wasted words. It front-loads the core purpose in the first sentence, followed by clear sections for 'Returns' and 'Raises'. Each sentence earns its place by providing essential information without redundancy, making it easy to parse quickly.

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 that there is an output schema (implied by 'Has output schema: true'), the description doesn't need to detail return values, and it appropriately summarizes them as 'List[Site]'. However, with no annotations, 0% schema description coverage for the single parameter, and missing behavioral details like authentication, the description is incomplete for a tool that interacts with an external API. It covers the basics but leaves too much unspecified for reliable use.

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

Parameters1/5

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

The input schema has one required parameter ('self') with 0% description coverage, meaning the schema provides no semantic information about this parameter. The tool description does not mention or explain the 'self' parameter at all, failing to compensate for the lack of schema documentation. This leaves the agent with no guidance on what this parameter represents or how to use it.

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: 'Retrieve all sites in the user's Bing Webmaster Tools account.' It specifies the verb ('Retrieve'), resource ('sites'), and scope ('user's Bing Webmaster Tools account'), making the intent unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_site_roles' or 'get_site_moves', which also retrieve site-related information, so it doesn't reach the highest score.

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 any prerequisites, such as needing an authenticated account, or compare it to similar sibling tools like 'get_site_roles' or 'get_site_moves'. The lack of usage context leaves the agent to infer when this tool is appropriate based on the name alone.

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