No user-submitted related servers found.
Scored across 14 tools
Each tool targets a distinct action, and the descriptions explicitly cross-reference the nearest neighbor to prevent misselection (am_recently_played vs am_top_played for recency vs play counts; am_search_songs vs am_resolve_candidates for lookup vs bulk grounding; am_audit_playlist vs am_analyze_flow for metadata vs audio features; am_analyze_flow vs am_optimize_order for diagnosis vs reordering). List vs show playlist boundaries are also clearly stated. No two tools appear to do the same thing.
All 14 tools use a uniform snake_case am_ prefix followed by a verb or verb_noun form (am_list_playlists, am_create_playlist, am_delete_playlist, am_search_songs, am_optimize_order). The pattern is predictable and readable throughout, with no mixed conventions.
14 tools fall squarely in the well-scoped 3-15 range and each earns its place: status, browse, search, resolve, CRUD, and three distinct analysis tools. Nothing feels redundant or padded for the curation domain.
The surface covers the full curation lifecycle (status, browse, search, resolve, create, add, delete, audit, analyze, optimize, tag steering). The main gap is that there is no remove-tracks-from-playlist or playlist metadata update/rename operation, though these are workable via delete-and-recreate.