Skip to main content
Glama
Sign In
nodriver-mcp-server

nodriver-mcp-server

by andresolbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Use persistent profile

use_profile
DestructiveIdempotent

Switch the browser to a named persistent profile to reuse cookies, logins, and extensions saved from a previous session. Restarts the browser and closes open pages; profile must already exist.

Instructions

Switch the browser to a named persistent profile.

Use it to pick up the cookies, logins and extensions stored in an earlier session. Startup defaults to a new tab; set_browser_flags(startup_mode=...) saves a different choice per profile. After an MCP server restart, select this same profile again to resume it.

Restarts the browser and closes every open page. The profile has to exist already — create it first with create_profile. Only one browser may use a profile at a time; a second instance pointed at the same one fails to start.

Input Schema

NameRequiredDescriptionDefault
nameYesName of an existing persistent profile, as shown by list_profiles. Pass "", "temp", "ephemeral" or "none" to switch back to an ephemeral profile.
browserNoWhich browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.default

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • addedInput schema / properties / browser
      Added value: +{
+  "default": "default",
+  "description": "Which browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.",
+  "type": "string"
+}
  2. First observedv1.7.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description goes well beyond by naming exactly what is destroyed ('Restarts the browser and closes every open page') and the concurrency constraint ('Only one browser may use a profile at a time; a second instance pointed at the same one fails to start'). This is the rare case where the description adds real behavioral value on top of annotations.

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 the action and purpose, then layers preconditions, side effects, and lifecycle in short declarative sentences. Each sentence carries distinct information (resume semantics, startup-mode cross-reference, restart requirement, prerequisite, exclusivity) with no restatement of the tool name or schema.

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 stateful, destructive browser-context switch, the description covers prerequisites, what gets closed, restart-time behavior, and the single-writer constraint; an output schema exists so return values need no explanation. An agent has everything needed to call it safely.

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% and the schema already explains both parameters, including the ephemeral escape values ('', 'temp', 'ephemeral', 'none') and the per-agent 'browser' naming. The description adds only indirect context (relevant to set_browser_flags(startup_mode=...) rather than to a parameter here), so the baseline 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?

States a specific verb+resource ('Switch the browser to a named persistent profile') and immediately frames the outcome (picking up cookies, logins, extensions from an earlier session). Dependencies on create_profile, list_profiles, and set_browser_flags clearly separate it from sibling tools like use_temp_profile and create_profile.

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?

Explicit when-to-use (resume a prior session's cookies/logins/extensions), a hard precondition ('The profile has to exist already — create it first with create_profile'), a post-restart rule ('After an MCP server restart, select this same profile again'), and an alternative for startup behavior ('set_browser_flags(startup_mode=...)'). Nothing is left to inference.

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