Skip to main content
Glama
Sign In
ZennoBrowser MCP Server

ZennoBrowser MCP Server

Official
by ZennoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Deletes multiple existing browser profiles.

bulk_delete_profile
DestructiveIdempotent

Delete multiple browser profiles at once by providing their UUIDs, optionally scoped to a workspace. Use it to remove several existing profiles in a single request.

Instructions

This method is used to delete several existing browser profiles at once.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "bulk_delete_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesTarget browser profile IDs (array of UUID).
workspaceIdNoWorkspace identifier. -1 means the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — it does not say deletion is permanent, what happens to profiles in use, or any auth/rate-limit constraints.

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?

A single efficient sentence with no wasted clauses. It is slightly padded by the 'This method is used to' opener but otherwise front-loads the action and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive bulk mutation with no output schema, the description omits whether deletion is irreversible, how partial failures are handled, and whether target profiles must be unlocked — meaningful gaps even though annotations cover the basic destructive flag.

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% for both parameters (body array of UUIDs, workspaceId with default -1), so the schema carries full meaning. The description adds no syntax or format detail beyond what the schema provides, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('delete several existing browser profiles at once'), and the 'several...at once' phrasing conveys the bulk scope that separates it from the single-profile delete_profile sibling. It is clear but never names or contrasts with any alternative tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus delete_profile or any other tool, no prerequisites, and no mention of workspace context needed to run it. The agent must infer the bulk-vs-single distinction from the name alone.

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