Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

submit_content

Submit URLs to Bing Webmaster Tools for indexing by providing HTTP messages and structured data, enabling search engine discovery of web content.

Instructions

Submit content for a specific URL.

Args: site_url: Site url E.g.: http://example.com url: Url to submit E.g.: http://example.com/url1.html http_message: HTTP message (base64 encoded) structured_data: Structured Data (base64 encoded) dynamic_serving: Device targeting (0-5). {none = 0, PC-laptop = 1, mobile = 2, AMP = 3, tablet = 4, non-visual browser = 5}

Raises: BingWebmasterError: If content cannot be submitted

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
urlYes
http_messageYes
structured_dataYes
dynamic_servingYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Specific registration of the 'submit_content' MCP tool by wrapping the external SubmissionService.submit_content method using wrap_service_method, which applies @mcp.tool() decorator.
    submit_content = wrap_service_method(mcp, service, "submission", "submit_content")  # noqa: F841
  • The wrap_service_method function creates the actual MCP tool handler (inner 'wrapper' async function decorated with @mcp.tool()) that executes the tool logic by delegating to the underlying service method (SubmissionService.submit_content). Preserves schema from original 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
  • Calls add_bing_webmaster_tools to register all Bing Webmaster tools, including 'submit_content', to the MCP server instance.
    add_bing_webmaster_tools(mcp, bing_service)
  • Instantiates the SubmissionService as an attribute of BingWebmasterService, which provides the underlying submit_content method used by the MCP tool.
    self.submission = submission.SubmissionService(self.client)
  • Maps the 'submission' service attribute to the SubmissionService class used for schema inspection and method retrieval in wrap_service_method.
    "traffic": traffic_analysis.TrafficAnalysisService,
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 an error case ('Raises: BingWebmasterError') but does not explain what 'submit' entails (e.g., is it an asynchronous process, does it require authentication, are there rate limits?). This leaves significant gaps for a tool that likely involves mutation or data submission.

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 well-structured with clear sections (Args, Raises) and uses bullet points for the enum. It is front-loaded with the core purpose. Some sentences could be more concise, but overall it avoids unnecessary verbosity.

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 complexity (6 parameters, no annotations, but has an output schema), the description is moderately complete. It covers parameter basics and an error case, but lacks behavioral context (e.g., submission process, side effects). The presence of an output schema mitigates the need to describe return values, but overall gaps remain for a mutation tool.

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?

Schema description coverage is 0%, so the description must compensate. It provides examples and explanations for parameters like 'dynamic_serving' with an enum mapping, adding value beyond the bare schema. However, parameters like 'self', 'http_message', and 'structured_data' are only briefly mentioned without detailed format or usage context, leaving some ambiguity.

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 action ('Submit content') and the target ('for a specific URL'), which is specific and actionable. It distinguishes from sibling tools like 'submit_url' or 'submit_url_batch' by focusing on content submission rather than URL submission, though the distinction could be more explicit.

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 is provided on when to use this tool versus alternatives like 'submit_url' or 'submit_feed'. The description lacks context about prerequisites, such as whether the site must be verified or if there are quota limits, which are hinted at by sibling tools like 'get_content_submission_quota'.

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