Stashr

Each tool has a clearly distinct purpose: saving vs. listing vs. searching vs. fetching vs. updating vs. managing collections/stats/account. Even fetch vs. fetch_many are explicitly scoped (single vs. batch with guidance on when to use each). No two tools appear to overlap in a way that would cause misselection.

Most tools follow a consistent verb_noun pattern (archive_bookmarks, list_bookmarks, save_bookmark, update_bookmark, list_collections, list_tags, library_stats, get_account). Minor deviation: 'fetch' and 'fetch_many' are verbs without a noun, and 'search' and 'view_media' are simpler but still readable. Overall, the pattern is predictable.

13 tools is within the sweet spot and each tool covers a distinct aspect of bookmark management: save, list, search, fetch (single/many), update, archive, tags, collections, stats, account, and media viewing. No tool feels superfluous, and the count matches the domain's breadth without bloat.

The surface covers the full lifecycle: create (save_bookmark), read (list/search/fetch), update (update_bookmark including archive, tags, favorite), delete (manage_collection for collections, but bookmark deletion is not exposed—though archive is reversible, which may suffice). Collections have create/read/update/delete. Stats and account info round out management needs. Missing direct bookmark deletion is a minor gap but archive serves as a reversible alternative.