Skip to main content
Glama
Lokii0911
by Lokii0911

go_back

Navigate one step back in browser history using Selenium. This tool simulates the browser's back button, enabling automated return to the previous page in test scripts.

Instructions

Navigate one step back in browser history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'go_back' MCP tool handler function. Defined with @mcp.tool() decorator, it calls browser.back() via the _run helper to navigate one step back in browser history.
    @mcp.tool()
    def go_back() -> dict[str, Any]:
        """Navigate one step back in browser history."""
        return _run("go_back", browser.back)
  • The BrowserManager.back() method that executes the actual browser back navigation by calling driver.back() on the Selenium WebDriver and returns the current browser state.
    def back(self) -> BrowserState:
        with self._lock:
            self._require_driver().back()
            return self.state()
  • The go_back tool is registered as an MCP tool via the @mcp.tool() decorator on line 65.
    @mcp.tool()
  • No input parameters are defined for go_back (no schema needed); it returns a dict[str, Any] (the browser state).
    def go_back() -> dict[str, Any]:
Behavior2/5

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

No annotations provided, so description must carry full burden. It does not disclose behavior like what happens at history start, whether it waits for page load, or any side effects.

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?

Single sentence, front-loaded, no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple, output schema exists, description is minimal but adequate for a straightforward action. Could mention behavior when history is empty.

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?

No parameters exist, so baseline is 4. Description adds no parameter info but that is fine since there are none.

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?

Description clearly states 'Navigate one step back in browser history', using a specific verb and resource. It distinguishes from sibling tools like go_forward and navigate.

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

Usage Guidelines3/5

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

Usage is implied by the name and description, but no explicit guidance on when to use vs alternatives or when not to use is provided.

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/Lokii0911/SeleniumMCP'

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