Skip to main content
Glama
andresolbach

nodriver-mcp-server

by andresolbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete profile

delete_profile
Destructive

Permanently remove a persistent Chrome profile, deleting its cookies, logins, history, and extensions. Requires switching away from the active profile first.

Instructions

Permanently delete a persistent Chrome profile directory.

Irreversible: the profile's cookies, logins, history and installed extensions are removed from disk, with no undo.

The active profile cannot be deleted — switch away with use_temp_profile first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the persistent profile to delete, as shown by list_profiles.
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.5/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses irreversibility, the exact data removed (cookies, logins, history, extensions), that deletion is from disk, and that there is no undo. It also states a behavioral restriction (active profile cannot be deleted). These details meaningfully exceed the annotation's binary signal and match it without contradiction.

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?

Three tight sentences — action first, then irreversibility/effects, then the key usage constraint. Every sentence carries information; there is no filler or redundancy beyond the deliberate emphasis on 'no undo'.

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?

The description covers what is deleted, permanence, the active-profile constraint, and how to work around it. An output schema exists to handle return values, annotations carry the destructive hint, and the schema documents the parameters. Nothing an agent needs to invoke it correctly 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?

Schema description coverage is 100%, so the parameters name and browser are already fully documented in the schema. The description adds no parameter-specific semantics beyond the general persistent-profile context; it neither enriches nor contradicts 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 'Permanently delete a persistent Chrome profile directory' — a specific verb, resource, and scope. It clearly distinguishes this from sibling tools like list_profiles, create_profile, use_profile, and use_temp_profile, leaving no ambiguity about what the tool does.

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 an explicit constraint and alternative: 'The active profile cannot be deleted — switch away with use_temp_profile first.' This addresses when not to use the tool and names the relevant sibling. It does not explicitly state general when-to-use scenarios, but the purpose makes the primary use case obvious.

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