Skip to main content
Glama
enesjakozh
dragons96

MCP-Undetected-Chromedriver

by dragons96
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

browser_get_visible_html

Extract the visible HTML content of a webpage using Chrome automation, bypassing anti-bot detection for reliable web scraping and testing.

Instructions

Get the HTML of the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_server_undetected_chromedriver/server.py:327-336 (handler)
    The primary handler and registration for the 'browser_get_visible_html' tool. Decorated with @mcp.tool() to register it in the MCP server. Ensures browser is initialized, retrieves the current page's HTML source using driver.page_source, and returns it wrapped in a success response.
    @mcp.tool()
async def browser_get_visible_html():
    """Get the HTML of the current page"""

    async def get_visible_html_handler(driver: uc.Chrome):
        return await create_success_response(driver.page_source)

    return await tool.safe_execute(
        ToolContext(webdriver=await ensure_browser()), get_visible_html_handler
    )

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe how it behaves—e.g., whether it returns only visible HTML, handles dynamic content, requires page load completion, or has any side effects. For a read operation with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is a single, clear sentence with zero wasted words. It is front-loaded with the core action and resource, making it immediately understandable. Every part of the sentence earns its place by directly conveying the tool's purpose without redundancy or fluff.

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 tool's simplicity (0 parameters, no annotations, no output schema), the description is adequate as a minimum viable explanation. It states what the tool does but lacks details on behavioral traits, output format, or usage context. For a read operation in a browser context, more completeness would include information on what 'visible HTML' entails or limitations, but it's not entirely inadequate.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to compensate for any parameter gaps, and it appropriately avoids unnecessary parameter details. A baseline of 4 is applied as it meets expectations for a parameterless tool without over-explaining.

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 ('Get') and resource ('HTML of the current page'), making the tool's purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'browser_get_visible_text', but the specificity of 'HTML' versus 'text' provides implicit distinction. This is not a tautology as it adds meaningful context beyond the tool name.

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 prerequisites (e.g., needing an active browser session), exclusions, or comparisons to siblings like 'browser_get_visible_text' for text extraction or 'browser_screenshot' for visual capture. Usage is implied by the action but lacks explicit context.

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

Related 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/dragons96/mcp-undetected-chromedriver'

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