chrome-dev-mcp

Overview Schema Source Related Servers Discussions Admin

navigate_tab

Destructive

Navigate the connected Chrome tab to a URL and wait up to 30 seconds for page load or pause; returns the outcome or call stack when a breakpoint stops the new page.

Instructions

Navigate the connected tab to a URL and wait up to 30s for the new page's load event — or for execution to pause first, e.g. on a breakpoint the new page hits during startup, in which case the call stack is returned. outcome is "loaded", "paused", "still-loading" (the new page is in place but its load event had not fired by the deadline), "same-document" (only the #hash changed; there is no load to wait for) or "download" (the URL was downloaded and the page did not change). Breakpoints carry over to the new page. Also works while paused, no need to resume first: the pause ends with the old page.

Input Schema

Name	Required	Description	Default
`url`	Yes	Absolute URL, including the scheme.

Output Schema

Name	Required	Description
`url`	No
`note`	No
`title`	No
`reason`	No	Pause reason. Present only when paused.
`outcome`	Yes	"loaded": the load event fired. "paused": execution paused before it did — see callStack. "same-document": only the #hash changed, so there is no load to wait for. "still-loading": the page committed but its load event did not fire in time. "download": the URL was handed to the download manager and the page did not change.
`callStack`	No	Same shape as get_debugger_state. Present only when paused.
`droppedBreakpoints`	No	Breakpoints set by `source` whose file has changed since: removed, and reported here once.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0Nov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the destructiveHint/openWorldHint annotations: it discloses the 30s deadline, the full set of possible outcomes, that breakpoints carry over to the new page, and that a pause is terminated by the old page. This is exactly the behavioral context an agent needs before invoking a navigation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and deadline, then enumerates outcomes compactly in one parenthetical. The outcome list makes the single sentence long and slightly dense, but no sentence is filler.

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?

Despite a single-parameter schema, the tool has complex timing and pause interactions; the description covers those fully. An output schema exists, so the outcome enumeration is bonus clarity rather than a necessity.

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?

Only one parameter and schema coverage is 100%, with the schema already stating 'Absolute URL, including the scheme.' The description adds no additional URL syntax or constraint detail, so the baseline of 3 applies.

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?

Specific verb and resource: 'Navigate the connected tab to a URL', with the added scope of waiting for the load event. It is clearly distinguishable from siblings like reload_tab and switch_tab, which do not take a URL or change the target document.

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?

Explicitly states it can be called while paused ('no need to resume first'), which is the main usage trap for this tool. It does not, however, explicitly name when to use this versus reload_tab or switch_tab, so it falls short of full alternative routing.

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