Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Delete bookmarks or folders

delete_bookmarks

Delete browser bookmarks or folders by ID, removing everything inside a folder. Runs as a dry run by default and only writes changes after you confirm.

Instructions

Deletes bookmarks and/or folders by id. Deleting a folder deletes everything inside it. Dry run by default.

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": {
      "ids": "<ids>"
    },
    "name": "delete_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
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.8/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does disclose the two most consequential behaviors: recursive deletion of folder contents and a non-destructive dry-run default. It omits irreversibility/no-undo and the force-flag hazard of an open browser overwriting the file, which the schema covers instead.

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 short, front-loaded sentences: identity, cascade consequence, safety default. Nothing is redundant and the destructive behavior is stated early.

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

Completeness4/5

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

For a destructive, unannotated tool with no output schema, the description covers the essential risks of cascade deletion and dry-run default. It leaves out no-undo semantics and whether the response lists affected items, gaps that are partly mitigated by the rich parameter descriptions.

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 75% and the schema already explains dry_run, force, and profile in detail. The description adds only the "by id" framing for the ids array, which is minimal beyond what the schema provides, so the baseline of 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 resource ("Deletes bookmarks and/or folders by id") and adds the key cascade rule that deleting a folder removes its contents. It does not explicitly contrast itself with delete_all_bookmarks or remove_empty_folders, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

The phrase "Dry run by default" implies a preview-then-confirm workflow, but the description never says when to prefer this over delete_all_bookmarks (bulk) or remove_empty_folders (cleanup), nor does it state prerequisites such as needing a profile id. Usage is implied rather than guided.

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