Skip to main content
Glama
dragons96

MCP-Undetected-Chromedriver

by dragons96

browser_go_back

Enables users to navigate back in the browser history within automated Chrome sessions, bypassing anti-bot detection for efficient web scraping, testing, and automation.

Instructions

Navigate back in browser history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The @mcp.tool() decorator registers the browser_go_back handler function, which safely executes driver.back() to navigate back in the browser history using shared helpers like ensure_browser and safe_execute.
    @mcp.tool()
    async def browser_go_back():
        """Navigate back in browser history"""
    
        async def go_back_handler(driver: uc.Chrome):
            driver.back()
            return await create_success_response("Navigated back in browser history")
    
        return await tool.safe_execute(
            ToolContext(webdriver=await ensure_browser()), go_back_handler
        )
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. It states the action but doesn't disclose behavioral traits such as whether it requires an active browser session, what happens if no history exists, or if it returns to the previous page or a specific point. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with zero waste. It's front-loaded with the core action, making it highly concise and well-structured for quick understanding.

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's complexity (simple navigation) but lack of annotations and output schema, the description is incomplete. It doesn't explain what happens on success (e.g., page change) or failure (e.g., error if no history), leaving gaps in understanding the tool's behavior and outcomes.

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 with 100% schema description coverage, so no parameter information is needed. The description appropriately doesn't mention parameters, aligning with the schema. A baseline of 4 is applied as it compensates adequately for the lack of parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Navigate back in browser history' clearly states the specific action (navigate back) and the resource (browser history). It distinguishes from siblings like browser_go_forward (forward navigation) and browser_navigate (general navigation), making the purpose explicit and differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (when browser history has previous pages) but doesn't explicitly state when to use this tool versus alternatives like browser_navigate or browser_go_forward. It provides clear context but lacks explicit exclusions or named alternatives, falling short of a perfect score.

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