Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

fetch_url

Submit URLs to Bing for immediate crawling and indexing through the Bing Webmaster Tools API. This tool triggers prompt URL fetching to update search engine results.

Instructions

Request Bing to fetch a specific URL immediately.

Args: site_url: The URL of the site url: The URL to fetch

Raises: BingWebmasterError: If URL cannot be fetched

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The generic handler wrapper function for all service methods, including fetch_url. Decorated with @mcp.tool() and calls the underlying SubmissionService.fetch_url method via dynamic getattr.
    # 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__
  • Specific registration of the 'fetch_url' tool by wrapping the submission service's fetch_url method.
    fetch_url = wrap_service_method(mcp, service, "submission", "fetch_url")  # noqa: F841
  • Invokes the function that registers all Bing Webmaster tools, including 'fetch_url', to the MCP server.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the SubmissionService instance (containing fetch_url implementation) as part of BingWebmasterService __aenter__.
    self.submission = submission.SubmissionService(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 of behavioral disclosure. It mentions that the tool 'fetches a URL immediately' and raises an error if unsuccessful, which hints at real-time execution and error handling. However, it omits critical details like authentication requirements, rate limits, side effects (e.g., on crawl budgets), or the nature of the fetch (e.g., indexing vs. preview). For a mutation tool with zero annotation coverage, this is insufficient.

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 concise and well-structured: a clear purpose statement followed by Args and Raises sections. Every sentence serves a purpose, with no wasted words. However, the lack of deeper context slightly reduces efficiency, as more information could enhance usability without adding bulk.

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's complexity (a mutation operation with 3 parameters, no annotations, but an output schema exists), the description is minimally adequate. It states the purpose and error conditions, and the output schema likely covers return values, reducing the need for that in the description. However, it misses key contextual elements like usage guidelines and parameter explanations, leaving gaps for effective agent 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 schema provides no parameter details. The description lists 'site_url' and 'url' in the Args section but doesn't explain their meanings, relationships, or formats (e.g., why both are required, what 'self' refers to). It adds minimal value beyond naming parameters, failing to compensate for the coverage gap.

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: 'Request Bing to fetch a specific URL immediately.' It specifies the action ('fetch'), the resource ('URL'), and the service ('Bing'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'submit_url' or 'get_fetched_urls', which handle related but distinct operations.

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 lacks context such as prerequisites (e.g., site verification), comparison with siblings like 'submit_url' (for queuing) or 'get_fetched_urls' (for listing), or any exclusions. This leaves the agent without clear direction on tool selection.

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