Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Delete ALL bookmarks

delete_all_bookmarks

Clear all bookmarks bar, other, and mobile bookmarks for a profile after creating a backup, with dry-run preview by default; use only after explicit confirmation and an export exists.

Instructions

Empties the bookmarks bar, Other bookmarks and Mobile bookmarks of a profile. A backup is made first. Only use after the user explicitly asked to wipe everything and an export exists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_all_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoWrite even if the browser seems to be open. Avoid: an open browser overwrites the file when it closes.
dry_runNoWhen true (default) nothing is written; the tool only reports what would change. Show that to the user and call again with dry_run=false after they confirm.
profileNoProfile id from list_profiles (e.g. "chrome:Default", "edge:Profile 1") or the full path to a Bookmarks file. Optional when only one profile exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the safety story. It does well to disclose that a backup is made first and that the operation is a full wipe, but it never states whether the change is reversible, how the backup relates to restore, or what conflicts with an open browser look like beyond what the schema says.

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?

Three short sentences, front-loaded with scope, then the backup guarantee, then the precondition. Nothing is wasted, though the middle sentence could be merged into the precondition to tighten it further.

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

Completeness3/5

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

For a destructive, zero-required-parameter tool with no annotations and no output schema, the description covers scope and the backup safeguard but leaves the agent without a described confirmation flow or return-value expectation. It is adequate rather than complete.

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% and each of force, dry_run and profile is documented in detail inside the schema, including the dry_run confirm-then-rerun workflow. The description adds no meaning beyond that, 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 and scope: it empties the bookmarks bar, Other bookmarks and Mobile bookmarks of a profile. The 'ALL folders' framing implicitly distinguishes it from a selective delete, but it never names a sibling tool to make the contrast explicit.

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?

Gives a hard precondition: only after the user explicitly asked to wipe everything and an export exists. That is a real when-to-use gate with an exclusions clause, though it does not point at concrete alternatives such as a selective delete or an export step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.