bookmark-organizer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOKMARKS_FILE | No | Path to a specific browser Bookmarks file to edit | |
| BOOKMARK_ORGANIZER_BACKUPS | No | Folder where automatic backups are stored (default: ~/.bookmark-organizer/backups) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_profilesA | Finds every Chromium-based browser profile (Chrome, Edge, Brave, Vivaldi, Opera, Chromium) on this computer that has bookmarks, with counts and whether the browser is open. |
| get_bookmarksA | Lists bookmarks and folders of a profile with their ids and folder path. Use folder_id to look inside one folder, and folders_only for a quick overview of the structure. |
| search_bookmarksB | Searches bookmark names, URLs and folder names (case-insensitive). |
| find_duplicatesB | Groups bookmarks that point to the same page (ignores http/https, www, trailing slash, #fragment and utm_* tracking parameters). |
| statsA | Overview of a profile: totals, top domains, empty folders, very old bookmarks. Good first step before proposing a cleanup. |
| check_linksA | Visits bookmarks over the network and reports the ones that look dead (404/410, DNS failure, connection refused). Sites that block bots (401/403/429) are reported separately as "uncertain", never as dead. |
| list_backupsA | Lists the automatic backups made before every change. |
| backupA | Makes a copy of the profile bookmarks file now. (Every write tool also does this automatically.) |
| restore_backupA | Puts a backup (from list_backups) back in place of the current bookmarks. The current state is backed up first, so this can be undone too. |
| delete_bookmarksA | Deletes bookmarks and/or folders by id. Deleting a folder deletes everything inside it. Dry run by default. |
| remove_duplicatesA | Keeps one copy of each page and deletes the others. Dry run by default. |
| create_folderA | Creates a folder path such as "Bookmarks bar/Work/Clients" (missing levels are created). Paths may start with "Bookmarks bar", "Other bookmarks" or "Mobile bookmarks"; otherwise the bookmarks bar is used. |
| add_bookmarkB | Adds a bookmark to a folder (by id or path, created if missing). |
| move_bookmarksA | Moves items into a folder. Give target_folder_id, or target_path (e.g. "Bookmarks bar/Study/Python") which is created when missing. For a big reorganization, call this once per destination folder with all the ids that go there. |
| renameC | Changes the name (and optionally the URL) of a bookmark, or the name of a folder. |
| sort_folderA | Sorts the contents of a folder alphabetically, folders first. Use recursive to sort every subfolder too. Without folder_id, sorts everything except the bookmarks bar top level (whose order users usually choose by hand). |
| remove_empty_foldersA | Deletes folders that contain no bookmarks (also folders that only contain empty folders). Dry run by default. |
| delete_all_bookmarksA | 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. |
| export_htmlA | Saves the bookmarks (all, or one folder) as a standard bookmarks .html file that any browser can import (Chrome, Edge, Firefox, Safari, Opera…). Does not change the browser. |
| import_htmlA | Loads a bookmarks .html file (exported from any browser or from the web tool) into a profile. mode "append": everything goes inside a new folder (default "Imported") in Other bookmarks. mode "replace": the current bookmarks are removed and the file becomes the new bookmarks (its toolbar folder goes to the bookmarks bar). Dry run by default. |
| preview_htmlB | Reads a bookmarks .html file and shows its folder structure and counts without importing anything. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Each tool targets a clearly distinct operation: discovery, reading, searching, duplicate detection vs removal, link checking, backups, deletion, folder/bookmark creation, moving, renaming, sorting, and import/export. The closest pairs (find_duplicates vs remove_duplicates, delete_bookmarks vs delete_all_bookmarks, preview_html vs import_html) are explicitly differentiated by dry-run/scope/read-only wording.
Most names follow a consistent snake_case verb_noun pattern (list_profiles, create_folder, move_bookmarks, export_html). A few tools use a bare verb or noun (stats, backup, rename) rather than a full verb_noun form, which is a minor deviation but still readable and predictable.
21 tools is on the higher side, but each covers a distinct bookmark-management concern: profile discovery, reading, search, analysis, backups, deletions, organization, and import/export. There is little redundancy, though the surface is slightly heavy for the domain.
The tool set covers the full lifecycle: profile discovery, bookmark reading/searching, stats, duplicate detection and cleanup, link checking, backup/restore, granular and bulk deletion, folder creation, bookmark addition, moving, renaming, sorting, empty-folder cleanup, and HTML import/export. Cross-profile copy is achievable via export/import, so there are no significant gaps.