Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

submit_feed

Submit sitemap feeds to Bing Webmaster Tools for website indexing. This tool sends your sitemap URL to Bing's search engine to help discover and index your web pages.

Instructions

Submit a sitemap feed for indexing.

Args: site_url: The URL of the site feed_url: The URL of the sitemap feed

Raises: BingWebmasterError: If feed cannot be submitted

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
feed_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core execution logic of the "submit_feed" tool handler. This anonymous function is decorated with @mcp.tool() and delegates the call to the underlying SubmissionService.submit_feed method after setting up the service context.
    # 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__
  • Registers the "submit_feed" tool by creating a wrapped handler using wrap_service_method.
    submit_feed = wrap_service_method(mcp, service, "submission", "submit_feed")  # noqa: F841
  • Invokes the addition of all Bing Webmaster tools to the MCP server, including the "submit_feed" tool.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the submission service instance (containing submit_feed) as an attribute of BingWebmasterService, used by the tool handler.
    self.submission = submission.SubmissionService(self.client)
  • Mapping of service names to classes, used by wrap_service_method to retrieve original method signature and docstring for the submit_feed tool.
    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 the tool 'submits' (implying a write/mutation operation) and raises an error on failure, but lacks details on permissions required, rate limits, idempotency, or what 'indexing' entails. This is insufficient for a mutation tool with zero annotation coverage.

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 efficiently structured with a clear purpose statement followed by Args and Raises sections. However, the inclusion of 'self' in the schema but not in the description creates a minor structural inconsistency, slightly reducing efficiency.

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 an output schema exists, the description doesn't need to explain return values. However, for a mutation tool with 3 parameters, 0% schema coverage, and no annotations, the description should provide more behavioral context (e.g., side effects, error conditions beyond the generic BingWebmasterError). It's minimally adequate but has clear gaps.

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 schema provides no parameter documentation. The description lists 'site_url' and 'feed_url' in the Args section, clarifying their roles, but omits 'self' entirely. This adds some value but leaves one parameter undocumented, resulting in partial compensation 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 action ('submit a sitemap feed for indexing') and identifies the resource ('sitemap feed'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'submit_url' or 'submit_content', which also involve submission actions for different resources.

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 like 'submit_url' or 'submit_content', nor does it mention any prerequisites or contextual constraints. The only implicit usage hint is the mention of 'BingWebmasterError', but this doesn't help with 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