Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_children_url_info

Retrieve information about child URLs for a specific parent URL in Bing Webmaster Tools. Use this tool to analyze website structure, identify linked pages, and monitor subpage details with filtering options.

Instructions

Retrieve information for child URLs of a specific URL.

Args: site_url: The URL of the site url: The parent URL to get child URL information for page: The page number of results to retrieve filter_properties: Properties to filter the results

Returns: List[UrlInfo]: List of URL information for child URLs

Raises: BingWebmasterError: If child URL information cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
urlYes
pageNo
filter_propertiesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the 'get_children_url_info' tool using wrap_service_method, which decorates it as an MCP tool (@mcp.tool()) and delegates execution to the underlying ContentManagementService.get_children_url_info method.
    get_children_url_info = wrap_service_method(  # noqa: F841
        mcp, service, "content", "get_children_url_info"
  • The dynamically generated handler function (wrapper) that executes the tool logic: binds to the service instance, calls the underlying service method 'get_children_url_info', and preserves the original signature and docstring.
    # 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__
  • Helper function that creates the MCP tool handler by inspecting the service method signature, decorating with @mcp.tool(), and proxying calls to the BingWebmasterService's content management service.
    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
  • Initializes and exposes the 'content' service attribute on BingWebmasterService, providing the ContentManagementService instance that contains the 'get_children_url_info' method.
    self.content = content_management.ContentManagementService(self.client)
  • Invokes the function that registers all Bing Webmaster tools, including 'get_children_url_info', 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 for behavioral disclosure. It mentions pagination ('page' parameter) and error handling ('Raises: BingWebmasterError'), but lacks critical details: whether this is a read-only operation, authentication requirements, rate limits, what 'child URLs' means operationally, or how results are structured beyond the return type. For a tool with 5 parameters and no 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with clear sections (Args, Returns, Raises) and is reasonably concise. However, the 'Args' section merely repeats parameter names without adding value, and the opening sentence could be more front-loaded with key constraints. Some sentences don't earn their place given the lack of semantic content.

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 complexity (5 parameters, 0% schema coverage, no annotations) and the presence of an output schema (which covers return values), the description is incomplete. It fails to explain parameter semantics, behavioral constraints, or usage context. While the output schema handles return values, the description doesn't adequately address the gaps in parameter understanding or operational guidance needed for effective tool 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 description must compensate. It lists parameter names in the 'Args' section but provides no semantic explanation beyond what's in the schema titles. Critical parameters like 'self' (purpose unclear), 'filter_properties' (what properties can be filtered?), and 'page' (how pagination works) lack meaningful context. The description adds minimal value over the bare schema.

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: 'Retrieve information for child URLs of a specific URL.' It specifies the verb ('retrieve'), resource ('information for child URLs'), and scope ('of a specific URL'). However, it doesn't explicitly differentiate from sibling tools like 'get_children_url_traffic_info' or 'get_url_info', which would be needed for a perfect 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. It doesn't mention sibling tools like 'get_children_url_traffic_info' (which appears related) or explain what distinguishes this tool from 'get_url_info'. There are no prerequisites, exclusions, or context for usage decisions.

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