Skip to main content
Glama
dragons96

MCP-Undetected-Chromedriver

by dragons96

browser_select

Automates selecting elements with Select tags on web pages using CSS selectors and specified values, ideal for web automation and scraping on sites with bot protection.

Instructions

Select an element on the page with Select tag

Args:
    selector: CSS selector for element to select - required
    value: The value to select - required

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes
valueYes

Implementation Reference

  • Implementation of the browser_select tool handler. Uses Selenium Select to choose an option by value in a dropdown.
    @mcp.tool()
    async def browser_select(
            selector: str,
            value: str,
    ):
        """Select an element on the page with Select tag
    
        Args:
            selector: CSS selector for element to select - required
            value: The value to select - required
        """
        assert selector, "Selector is required"
        assert value, "Value is required"
    
        async def select_handler(driver: uc.Chrome):
            select = Select(driver.find_element(By.CSS_SELECTOR, selector))
            select.select_by_value(value)
            return await create_success_response(f"Selected {selector} with: {value}")
    
        return await tool.safe_execute(
            ToolContext(webdriver=await ensure_browser()), select_handler
        )
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 states the action ('select an element') but lacks crucial behavioral details: whether this requires the page to be in a specific state, what happens if the element isn't found, whether it triggers page changes, what the expected outcome is, or any error conditions. The description provides only basic operational information without 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.

Conciseness4/5

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

The description is appropriately sized with a clear purpose statement followed by parameter explanations. The two-sentence structure is efficient, though the parameter documentation could be more integrated. No wasted words, but the formatting with 'Args:' header feels slightly verbose for such a simple tool.

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 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. While it explains what the tool does and what parameters mean at a basic level, it lacks information about return values, error conditions, behavioral constraints, and how this tool differs from similar siblings. For a browser interaction tool with no structured metadata, more context is needed.

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?

Schema description coverage is 0%, so the description must compensate. It adds basic semantics for both parameters: 'selector: CSS selector for element to select - required' and 'value: The value to select - required'. This explains what each parameter represents, but doesn't provide format examples, constraints, or relationship between parameters. The description adds value beyond the bare schema but doesn't fully compensate for the 0% coverage.

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: 'Select an element on the page with Select tag' - this specifies the verb ('select'), resource ('element on the page'), and target type ('Select tag'). It distinguishes from siblings like browser_click or browser_fill by focusing specifically on dropdown/select elements. However, it doesn't explicitly contrast with all sibling tools.

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. While the mention of 'Select tag' implies it's for dropdown elements, there's no explicit comparison to other tools like browser_click or browser_fill that might handle similar interactions. No prerequisites, exclusions, or alternative scenarios are mentioned.

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