Skip to main content
Glama
andresolbach

nodriver-mcp-server

by andresolbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Close browser

close_browser
Destructive

Closes the entire Chrome browser and all its tabs at once, unlike closing just a page. Useful for applying launch flags or discarding temporary profile data, with automatic relaunch on the next call.

Instructions

Quit Chrome entirely, closing every tab.

Unlike close_page (which always keeps one tab alive), this tears down the whole browser. Chrome relaunches automatically on the next tool call with the currently selected profile, so this is also how you apply pending launch flags without switching profiles.

On an ephemeral temp profile (the default) this discards cookies, logins and localStorage — save_session first if you need them back. Persistent profiles created with create_profile keep everything.

It keeps the browser itself. The name, its selected profile and its launch flags survive for the next relaunch, so the name goes on counting against the 12-browser limit. When an agent is finished for good, call shutdown_browser instead: it also releases the name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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

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.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes far beyond: it details that cookies/logins/localStorage are discarded on temp profiles but preserved on persistent ones, that the browser relaunches automatically, that the name/profile/flags survive and count against the 12-browser limit. This adds critical behavioral context that annotations alone don't provide. No contradiction with 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 longer than a typical one, but every sentence earns its place: main purpose, contrast with close_page, behavior on relaunch, side effects on temp vs persistent profiles, persistence of name, and the alternative shutdown_browser. It is front-loaded with the core action and uses structured paragraphs. Slightly verbose but not wasteful — well organized.

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 description is remarkably complete. It covers all relevant behaviors: what happens to cookies/data, what persists across relaunch, the browser limit, and the distinction from shutdown_browser. An output schema exists, so return values need not be explained. Nothing an agent needs to correctly invoke or decide when to use this tool is missing.

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?

The input schema for the single 'browser' parameter is fully described (100% coverage) and includes a clear explanation of what each name represents and how to use the default. The tool description itself does not add any additional meaning about the parameter — it focuses on the tool's overall behavior. Since the schema already covers the parameter semantics thoroughly, a baseline of 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 clearly states the tool 'Quit Chrome entirely, closing every tab' — a specific verb and resource. It explicitly contrasts with close_page (which keeps one tab alive) and shutdown_browser (which releases the name), making sibling differentiation unambiguous. An agent can immediately tell what this tool does and how it differs from close_page and shutdown_browser.

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?

It gives explicit when-to-use guidance: it mentions it's how you apply pending launch flags without switching profiles, and when to use shutdown_browser instead ('When an agent is finished for good'). It also advises calling save_session first on temp profiles to preserve data. This is strong, actionable routing to the correct tool in different scenarios.

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