Skip to main content
Glama
andresolbach

nodriver-mcp-server

Open new page

new_page

Opens a new browser tab and loads a URL, with options for device emulation and isolated contexts to manage multiple sessions.

Instructions

Open a new browser tab and load a URL.

Chrome always starts with one tab, so the first call here reuses that empty startup tab rather than leaving a stray blank page behind for the rest of the session. A blank tab sitting among others is left alone, and an isolated context always gets a target of its own.

Unless background is set, the new page becomes the selected page for every subsequent tool call.

Passing device applies emulation before the first real request, so mobile signals are present from the very first byte — which calling emulate_device afterwards cannot achieve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to load in the new tab, including the scheme. Defaults to "about:blank" for an empty tab.about:blank
deviceNoDevice to emulate — sets user agent, UA client hints, viewport, device pixel ratio and touch together. Presets: "pixel_7" (aliases: pixel7, android, android_phone), "pixel_7_landscape" (pixel7_landscape, android_landscape), "ipad_air" (ipadair, ipad, tablet). Case, spaces and -/_ are normalised. Empty string leaves emulation unchanged.
timeoutNoMaximum wait in milliseconds. 0 uses the built-in default.
backgroundNoOpen the tab without focusing it, leaving the current page selected. Default false, which focuses the new page and makes it the target of all following tool calls.
isolated_contextNoOpen the page in a named isolated browser context — its own cookie jar and storage, comparable to a separate incognito window. Pages given the same name share that context; different names are fully isolated from each other. Use it to hold several logins to one site at once. Empty string uses the normal shared context.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses significant behavioral traits: reuse of the startup tab, selection for subsequent tool calls, device emulation before the first request, and isolated context behavior. This adds substantial context that annotations alone do not provide.

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 compact and front-loaded with the core action. Each sentence contributes valuable behavioral or contextual information without redundancy or filler. It is long enough to cover key nuances but still 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?

Given the tool's complexity, the annotations, and the presence of an output schema, the description covers essential behaviors: tab reuse, selection semantics, emulation timing, and isolated contexts. No critical operational details are missing, and the description is fully sufficient to guide correct invocation.

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?

The schema already covers all 100% of parameters with descriptions, so the baseline is 3. The description adds extra meaning by explaining the timing implications of device emulation, the effect of background on page selection, and how isolated_context names create shared or isolated environments—information not just repeating the schema.

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 opens with a specific action: "Open a new browser tab and load a URL," which clearly identifies the tool's purpose and resource. It distinguishes itself from sibling tools like navigate_page by specifying that it creates a new tab rather than navigating the current one.

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?

The description provides clear context: it explains the first-call behavior in Chrome, the default selection behavior unless background is set, and explicitly references emulation timing compared to emulate_device. It does not explicitly list exclusions or alternatives beyond emulate_device, but the context is sufficient for most use cases.

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/andresolbach/nodriver-mcp-server'

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