seleniumbase-mcp

Official

Overview Schema Source Related Servers Discussions Admin

navigate

Open a specified URL in the current browser tab, adding 'https://' if no protocol is given. Waits for navigation to complete, then confirms the requested destination for direct page access.

Instructions

Navigate the current browser tab to a URL.

Use this when the browser needs to visit a new URL rather than move through its existing back/forward history.

If the URL does not include a protocol such as "https://", SeleniumBase automatically prefixes "https://" before navigation. For example, "seleniumbase.io" becomes "https://seleniumbase.io".

Navigation waits for the browser's navigation operation to complete before returning. Dynamic content may still be loading; use wait_for when synchronization is required.

Args: url: Destination URL. May be a complete URL such as "https://example.com" or a hostname such as "example.com".

Returns: A confirmation message containing the requested URL.

Tool selection: - Go to a new URL -> use navigate. - Return to the previous page -> use manage_history(action="back"). - Go forward in history -> use manage_history(action="forward"). - Refresh the current page -> use manage_history(action="reload").

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 23, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden. It explains the automatic https:// prefix, that navigation waits for the browser operation to complete, and that dynamic content may still load, recommending wait_for for synchronization. These are non-obvious and valuable behavioral details.

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 well organized with front-loaded purpose, a short args section, and a dedicated tool-selection list. Each sentence adds relevant information without redundancy, making it easy to scan.

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

Completeness5/5

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

For a single-parameter navigation tool with an output schema, the description covers the core behavior, parameter semantics, waiting behavior, and alternative tool routing. It is complete enough for an agent to invoke it correctly without additional inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no description for the url parameter (0% coverage), so the description must compensate. It does so by defining the parameter as a destination URL and giving both complete URL and hostname examples, clarifying accepted formats.

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 the tool navigates the current browser tab to a URL, with a specific verb and resource. It also distinguishes navigate from history-based movement (back/forward/reload), making its purpose unambiguous relative to siblings.

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

Usage Guidelines5/5

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

The description explicitly says when to use navigate versus manage_history, including a clear tool-selection section: new URL -> navigate, back/forward/reload -> manage_history. This gives an agent direct decision guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.