Skip to main content
Glama
bookmark-organizer

bookmark-organizer

by dpfcarlos

Remove empty folders

remove_empty_folders

Deletes empty bookmark folders, including nested folders that contain only empty folders; reports changes without writing by default.

Instructions

Deletes folders that contain no bookmarks (also folders that only contain empty folders). Dry run by default.

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": "remove_empty_folders"
  }
}

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

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

With no annotations supplied, the description carries the full behavioral burden and does disclose the two most consequential traits: recursion into nested empty folders and a safe-by-default dry run. It omits that removal is irreversible, that an open browser can overwrite the file on close, and what the dry-run report contains — all of which live only in the schema parameter text.

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?

Two short sentences, zero filler, with the scope definition front-loaded ahead of the dry-run safety note. Every clause earns its place and nothing is repeated from structured fields beyond the one default worth surfacing.

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 cleanup tool with no annotations and no output schema, the definition covers purpose and the safe default but leaves the agent without a description of the dry-run report format or the browser-open caveat. These gaps are patched by the schema text, but the description alone is only adequate.

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 force, dry_run, and profile are already fully documented, including the confirm-then-rerun workflow. The description's only parameter-relevant statement, 'Dry run by default,' merely restates the dry_run default and adds no new meaning.

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 folders) and narrows scope precisely to folders holding no bookmarks, including the recursive case of folders containing only empty folders. That is enough to tell it apart from delete_bookmarks or delete_all_bookmarks by resource type, though it never explicitly contrasts itself with any sibling.

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?

Usage is only implied: the scoping to empty folders suggests a post-cleanup tidy-up step, and 'Dry run by default' hints at a review-then-confirm flow. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for agents deciding between this and delete_bookmarks or sort_folder.

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