No user-submitted related servers found.
Scored across 37 tools
Most tools have clearly distinct purposes (listens, stats, metadata, feedback, pins, playlists, etc.). A few could be confused—e.g., get_user_stats vs get_activity_stats both deal with stats, and manage_recording_feedback vs manage_recommendation_feedback are similar—but the detailed descriptions and parameter sets make each tool's role clear enough to prevent misselection.
The naming predominantly follows a consistent get_/manage_/submit_ pattern (get_listens, get_user_stats, manage_playlist, submit_listen). Exceptions like 'lb_radio' and 'generate_cover_art' break the pattern slightly, but they are still readable and self-explanatory. Overall, the conventions are predictable with a few outliers.
At 37 tools, the surface is substantial, but it corresponds to a complete API wrapper for ListenBrainz. Each tool bundles multiple related endpoints (e.g., manage_playlist covers 9 actions), so the functional scope is well-managed. It sits at the high end of 'reasonable' for a full-featured service, not sprawling or redundant.
The tool set covers the major ListenBrainz domains: listening data (submit/get/manage), statistics (user/sitewide/activity), metadata lookup and mapping, recommendations and feedback, pins, follows, playlists (create/edit/delete/copy/export/import), feed and timeline events, cover art generation, and settings/status. It includes both read and write operations, and even handles edge cases like token validation and dump info. No obvious dead ends or missing lifecycle steps.