Skip to main content
Glama
dragons96

MCP-Undetected-Chromedriver

by dragons96

browser_click

Automate clicking on web page elements using selectors with a Chrome browser tool designed to bypass anti-bot detection for scraping, testing, and automation tasks.

Instructions

Click an element on the page

Args:
    selector: The selector of the element to click - required

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes

Implementation Reference

  • Main handler and registration for browser_click tool using @mcp.tool(). Executes Selenium click on element selected by CSS selector after ensuring browser instance.
    @mcp.tool()
    async def browser_click(
            selector: str,
    ):
        """Click an element on the page
    
        Args:
            selector: The selector of the element to click - required
        """
        assert selector, "Selector is required"
    
        async def click_handler(driver: uc.Chrome):
            driver.find_element(By.CSS_SELECTOR, selector).click()
            return await create_success_response(f"Clicked element: {selector}")
    
        return await tool.safe_execute(
            ToolContext(webdriver=await ensure_browser()), click_handler
        )
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 clicking but fails to explain what happens after the click (e.g., page navigation, event triggers), error conditions (e.g., if selector not found), or side effects. 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.

Conciseness4/5

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

The description is brief and front-loaded with the core action, followed by a parameter note. It avoids unnecessary verbosity, though the formatting with 'Args:' could be more integrated. Overall, it's efficient but could be slightly more polished.

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?

For a tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover behavioral aspects like error handling, return values, or interaction with sibling tools, making it inadequate for safe and effective use by an AI agent.

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?

The description adds minimal value beyond the input schema, which has 0% coverage. It specifies that 'selector' is required and identifies it as 'the selector of the element to click', but doesn't elaborate on selector syntax, examples, or constraints. Given the low schema coverage, this provides some compensation but is insufficient for full clarity.

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 ('click') and target ('an element on the page'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'browser_iframe_click', which performs a similar action in a different context, preventing 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?

No guidance is provided on when to use this tool versus alternatives like 'browser_iframe_click' or other interaction methods. The description lacks context about prerequisites (e.g., whether a page must be loaded) or exclusions, offering minimal usage direction.

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