Skip to main content
Glama
isiahw1

mcp-server-bing-webmaster

add_deep_link_block

Block specific URL patterns from appearing as deep links in Bing search results to control site visibility.

Instructions

Block deep links for specific URL patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYes
url_patternYes
block_typeYes
reasonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'add_deep_link_block' tool. It takes site_url, url_pattern, block_type, and reason as inputs, makes a POST request to the Bing Webmaster API endpoint 'AddDeepLinkBlock', and returns a success message.
    async def add_deep_link_block(
        site_url: Annotated[str, "The URL of the site"],
        url_pattern: Annotated[str, "URL pattern to block"],
        block_type: Annotated[str, "Type of block"],
        reason: Annotated[str, "Reason for blocking"],
    ) -> Dict[str, str]:
        """
        Block deep links for specific URL patterns.
    
        Args:
            site_url: The URL of the site
            url_pattern: URL pattern to block
            block_type: Type of block
            reason: Reason for blocking
    
        Returns:
            Success message
        """
        async with api:
            await api._make_request(
                "AddDeepLinkBlock",
                "POST",
                {
                    "siteUrl": site_url,
                    "urlPattern": url_pattern,
                    "blockType": block_type,
                    "reason": reason,
                },
            )
            return {"message": f"Deep link block for {url_pattern} added successfully"}
  • The @mcp.tool decorator registers the 'add_deep_link_block' tool with the MCP server, specifying its name and description.
    @mcp.tool(
        name="add_deep_link_block",
        description="Block deep links for specific URL patterns.",
    )
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 states the tool blocks deep links, implying a mutation, but doesn't specify permissions required, whether the block is reversible, or any rate limits. This leaves significant gaps for a tool that likely modifies system settings.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a basic tool, though it could be more informative given the lack of other context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters with 0% schema coverage, no annotations, and likely performs a mutation (blocking), the description is insufficient. It doesn't explain parameters, behavioral traits, or usage context, and while an output schema exists, the description doesn't address core operational aspects needed for safe and effective 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 mentions 'specific URL patterns' but doesn't explain the four parameters (site_url, url_pattern, block_type, reason) or their relationships. It adds minimal value beyond the schema's structure.

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 ('Block') and resource ('deep links for specific URL patterns'), making the purpose understandable. It doesn't explicitly distinguish from sibling tools like 'add_blocked_url' or 'add_page_preview_block', which appear to have related blocking functions, so it misses 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 like 'add_blocked_url' or 'remove_deep_link_block'. It lacks context about prerequisites, such as whether a site must be configured first, or any exclusions for usage.

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/isiahw1/mcp-server-bing-webmaster'

If you have feedback or need assistance with the MCP directory API, please join our Discord server