Skip to main content
Glama
Sign In
ZennoBrowser MCP Server

ZennoBrowser MCP Server

Official
by ZennoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Deletes the specified profile folder.

delete_profile_folder
DestructiveIdempotent

Delete a browser profile folder by its UUID, optionally within a workspace, to remove unused or obsolete profiles. Requires the folder to exist in the specified workspace.

Instructions

This method is used for deleting a profile folder. The profileFolderId value must match the existing folder in the specified workspace.

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": {
      "profileFolderId": "<profileFolderId>"
    },
    "name": "delete_profile_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdNoWorkspace identifier. -1 means the default workspace.
profileFolderIdYesUnique identifier of the profile folder to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety and idempotency are covered. The description only restates a generic precondition ('must match the existing folder') and never discloses what happens to the profiles contained in the folder — the single most important behavior for a destructive delete that has a '..._with_contents' counterpart.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded, but the opening sentence ('This method is used for deleting a profile folder') largely restates the title and wastes the space that could have carried the missing behavioral detail. Not verbose, but not efficient either.

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 tool with several overlapping delete siblings and no output schema, the description is too thin. It omits the folder-contents semantics and the alternative-tool routing an agent needs to invoke 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 description coverage is 100%, so both workspaceId (default -1) and profileFolderId (uuid) are fully documented in the schema. The description adds only a light existence precondition for profileFolderId and nothing about workspaceId, so baseline 3 applies.

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 (deleting) and resource (a profile folder), so the basic operation is unambiguous. However, it fails to distinguish itself from the near-identical sibling delete_profile_folder_with_contents, leaving the agent unable to tell the two apart from the description alone.

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?

No when-to-use guidance, prerequisites, or alternatives are given. The critical question of when to pick this over delete_profile_folder_with_contents or delete_profile is never addressed, and no conditions or exclusions are stated.

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