Skip to main content
Glama
Sign In
WebDriverIO MCP Server

WebDriverIO MCP Server

Official
by webdriverio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

navigate

Idempotent

Loads a specified URL in the current browser tab and waits for the page load event, resetting page state. Use it when the target URL is known instead of clicking links.

Instructions

Loads a URL in the current tab and waits for the page load event. Resets page state — DOM, JS runtime, timers, and frame context are destroyed. Use instead of clicking links when the target URL is known.

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to navigate to
sessionNoTarget session: map name or sessionId. Omit to use the default session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.1.0
    • addedInput schema / properties / session
      Added value: +{
+  "description": "Target session: map name or sessionId. Omit to use the default session.",
+  "type": "string"
+}
  2. Addedv3.11.1
  3. Removedv3.11.0
  4. Added
  5. Removedv3.5.1
  6. Addedv3.4.4
  7. Removedv3.4.1
  8. First observedv2.5.0

TDQS

A4.6/5.0
Behavior5/5

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

Discloses side effects beyond the annotations: page state is reset, DOM, JS runtime, timers and frame context are destroyed, and the call blocks until the load event fires. That destruction note is a genuine and important disclosure that the annotations (idempotentHint=true, destructiveHint=false) do not carry; the annotations describe the abstract safety profile for external data, while the description correctly tells the agent that in-page state is lost.

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?

Three short sentences, zero filler, and the operational effect (load + wait) is front-loaded before the destructive detail and the alternative. Every sentence carries distinct information.

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?

Covers timing (waits for load event), state loss, and tool choice, which is what an agent needs to sequence navigation correctly. With no output schema, it does not say what the call returns (e.g., whether fresh page content is included or a snapshot call is required afterward), which is a real remaining gap.

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 coverage is 100%, with both url and session documented in-schema, so the baseline applies. The description adds only the implicit notion that navigation happens in "the current tab" and does not explain the session parameter's targeting behavior or what happens when it is omitted.

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?

Uses a specific verb+resource ("Loads a URL in the current tab") and states the completion condition ("waits for the page load event"). This is clearly distinguishable from siblings like click_element, switch_tab, and start_session without opening any schema.

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?

Explicitly names the alternative: "Use instead of clicking links when the target URL is known." That is a direct when-to-use / when-to-prefer-other-tool rule an agent can act on.

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

Deploy Server

Other Tools