Skip to main content
Glama
Vitexus

mcp-server-webdriver

by Vitexus

browser_open

Opens a URL in Firefox, starting a new browser session if needed. Captures JavaScript errors, console output, and network requests with BiDi.

Instructions

Open URL in Firefox. Starts a new browser session if none is running.

With enable_bidi=True (default) the session automatically captures: • All JavaScript exceptions (file, line, column, stack trace) • All console.* output (log / warn / error / info / debug) • All network requests with status codes and durations

geckodriver sources (priority order):

  1. GECKODRIVER_PATH env → 2. apt install gecko-driver → 3. webdriver-manager

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to open
headlessNoHeadless mode (no visible window)
enable_bidiNoEnable WebDriver BiDi for DevTools capture (JS errors, console, network). Requires Firefox + geckodriver ≥ 0.34. Default True.
geckodriver_logNoOptional file path for geckodriver log
firefox_binaryNoOptional path to a custom Firefox binary

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses BiDi capture features and driver sourcing logic beyond the readOnlyHint=false annotation, though session management details could be clearer.

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?

Front-loaded with purpose, then two focused paragraphs on BiDi and driver sourcing; no wasted sentences.

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?

Covers main behaviors but omits error handling and return value context; output schema presumably fills return details.

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?

Adds value beyond the schema by explaining BiDi behavior and driver priority; schema coverage is 100% but description provides operational context.

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 clearly states 'Open URL in Firefox' and specifies session behavior, effectively differentiating from sibling navigation tools.

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?

No explicit guidance on when to use or avoid this tool versus alternatives; only implicit through functional 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

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/Vitexus/mcp-server-webdriver'

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