Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

remove_feed

Remove previously submitted sitemap feeds from Bing Webmaster Tools to manage site indexing and crawl efficiency.

Instructions

Remove a previously submitted sitemap feed.

Args: site_url: The URL of the site feed_url: The URL of the feed to remove

Raises: BingWebmasterError: If feed cannot be removed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
feed_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the 'remove_feed' MCP tool by calling wrap_service_method, which creates and decorates a wrapper function with @mcp.tool() that delegates to BingWebmasterService.submission.remove_feed.
    remove_feed = wrap_service_method(mcp, service, "submission", "remove_feed")  # noqa: F841
  • The dynamically generated handler function for the 'remove_feed' tool. It uses the service instance to call submission.remove_feed with the input arguments, preserving the original method's signature and documentation.
    @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__
  • Mapping of service attribute names to their classes, used by wrap_service_method to get the original method signature for 'submission.remove_feed'.
    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,
    }
  • Initializes the 'submission' service attribute on BingWebmasterService, which provides the 'remove_feed' method instance used by the tool handler.
    self.submission = submission.SubmissionService(self.client)
  • Calls the function that registers all Bing Webmaster tools, including 'remove_feed', to the MCP server.
    add_bing_webmaster_tools(mcp, bing_service)
Behavior2/5

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

With no annotations provided, the description carries full burden. It states the tool performs a removal action (implying mutation) and mentions potential errors, but lacks critical behavioral details: whether this is destructive/permanent, what permissions are required, if it affects indexing, or typical response format. The error note adds some value but doesn't compensate for missing behavioral context.

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 appropriately brief but could be better structured. The first sentence clearly states the purpose, but the Args/Raises sections, while helpful, are formatted as documentation rather than integrated prose. It's front-loaded with the main action, but the formatting slightly reduces readability for an agent.

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 3 parameters with 0% schema coverage and no annotations, the description does moderately well by explaining parameter meanings and noting error conditions. However, as a mutation tool with potential side effects, it should provide more behavioral context (e.g., permanence, effects on indexing). The presence of an output schema helps, but the description doesn't reference it or explain what 'success' looks like.

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

Parameters4/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 explicitly documents all 3 parameters with brief explanations ('site_url: The URL of the site', 'feed_url: The URL of the feed to remove'), adding meaningful semantics beyond the bare schema. The 'self' parameter is not explained, but with 2/3 parameters covered and clear mapping to the operation, this provides substantial value.

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 ('Remove') and target ('a previously submitted sitemap feed'), making the purpose immediately understandable. It distinguishes from sibling tools like 'remove_blocked_url' or 'remove_site' by specifying the resource type. However, it doesn't explicitly contrast with similar removal tools in the sibling list.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., that a feed must exist first), nor does it reference sibling tools like 'submit_feed' or 'get_feeds' for context. The error handling note about 'BingWebmasterError' implies usage constraints but doesn't specify them.

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