Skip to main content
Glama
andresolbach

nodriver-mcp-server

by andresolbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create profile

create_profile
Idempotent

Create a named persistent Chrome profile that preserves cookies, logins, and extensions across sessions, so sites stay logged in between runs.

Instructions

Create a named persistent Chrome profile — a reusable user-data dir.

A persistent profile keeps cookies, logins and Web Store extensions between runs, so a site you log into once stays logged in. It is the sturdier alternative to save_session / load_session.

Creating one is harmless by itself: nothing changes until you activate it, here or via use_profile. An existing profile of the same name is left untouched rather than overwritten. Profiles live under ~/.nodriver-mcp/profiles/.

Only one browser instance can use a given profile at a time, so give concurrent setups different names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProfile name, e.g. "google-login". Only letters, digits, "-" and "_" are kept; any other character is stripped out.
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
activateNoSwitch to the new profile straight away. That restarts the browser and closes all open pages. Default false, which only creates the directory.

Output Schema

TableJSON 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.1/5.0
Behavior4/5

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

Annotations already convey idempotentHint=true and destructiveHint=false, and the description reinforces and extends this by saying creation is harmless until activation, existing profiles are left untouched rather than overwritten, and profiles live under ~/.nodriver-mcp/profiles/<name>. It also discloses the single-instance constraint, which is valuable behavioral context beyond the annotations.

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?

The description is compact and front-loaded with the core purpose, followed by persistence semantics, safety, storage location, and concurrency warning. Each paragraph earns its place, though there is slight redundancy with the browser parameter's 'parallel agents each need their own name' note.

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?

For a tool with three parameters, an output schema, and strong annotations, the description covers the important behavioral ground: what persistence means, when activation happens, that creation is non-destructive, where files live, and the concurrency limitation. It is complete enough for an agent to select and invoke the tool 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 description coverage is 100%, so the schema already documents name, browser, and activate thoroughly. The description adds a bit of extra context around profile storage location and concurrency, but it does not substantially change or deepen parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

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 verb and resource: 'Create a named persistent Chrome profile' and immediately clarifies it is a reusable user-data dir. It also differentiates itself from siblings by calling out save_session/load_session as a weaker alternative and mentioning use_profile as a later activation path.

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 gives clear usage context: use a persistent profile when you want cookies, logins, and extensions to survive between runs, and it explicitly names save_session/load_session as the alternative. It also gives practical guidance about concurrent browser instances needing different names. It stops short of an explicit 'use this instead of X when...' matrix, but the comparison is strong.

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