Counts and averages of the loaded playlists grouped by one dimension (optionally also split by a second one), as a small table you can chart. Examples: decade x playlist, top 20 artists, tracks per genre family, additions per month, one artist's albums (filters.artist).

Args: group_by: decade, year, artist (primary), album, genre (exact tags), genre_family, playlist, month_added or popularity_bin (steps of 5). split_by: optional second dimension from the same list; one row per group x split value. metrics: any of unique_tracks, entries, hours, avg_popularity, share (% of the selection's unique tracks). Default: unique_tracks and share. filters: narrow the tracks first (same filters as find_tracks). limit: groups to return, biggest first (default 50, max 500). Time dimensions and popularity bins are returned in order.

One row per playlist (or only the ones given): size, followers, hours, average, shortest and longest duration, average popularity, genre diversity, release era (median, oldest, newest year), first and last added, and the unique tracks that are in no other playlist; then how many tracks each pair of playlists shares. A data tool: draw charts from it yourself.

Args: playlists: names, IDs or links; default all loaded playlists.

Connect Tailorlist to the user's Spotify account (only needed once).

Returns who is connected, or a login link the user has to open in their browser. After they approve access, call this again to confirm.

Change a draft, then refresh its page. All the changes are applied in order, or none if one fails. Only the draft (and the organize progress it touches) changes; nothing is written to Spotify.

Args: draft: the draft ID ("d3"). changes: a list of operations, each with an "op": rename {group, to}; move {tracks, to, from_group?, create_if_missing?} between groups; assign {tracks, to} puts unmatched tracks in a group (saved as manual progress, like the original's "Save assignments"); drop_group {group} (its tracks stay in the pool, listed as left out); merge {groups, into?}; keep_visible {group, on?} (its tracks aren't marked done when written); skip_unmatched {} (marks the unmatched tracks without data as done, so they leave the pool); reopen {group} (a done group counts as not done). tracks picks tracks by artist, text (in the name), genre, genre_family, decade, year_from/to, popularity, track_ids, reason (unmatched only) or all=true. Group names accept a unique part.

Fill in the genres Spotify leaves empty, using MusicBrainz (free, about 1 request per second).

Runs in the background and returns at once; call it again to see progress (it never starts a second run). Only primary artists with no Spotify genres are looked up, the most-used first; results are saved as they arrive, so every other tool uses them right away and a stopped run resumes where it left off. Takes a few minutes per hundred artists. Start it only if the user agrees.

Duplicates among the loaded playlists (or only the ones given): exact duplicates (the same Spotify ID saved more than once, inside or across playlists) and different versions (same song name and primary artist under different IDs), each with the playlists it is in and the IDs.

Args: playlists: names, IDs or links; default all loaded playlists. kind: "all", "exact" or "versions". limit: rows per list (default 50, max 500).

List unique tracks of the loaded playlists that pass the filters: track, artist, album, year, duration, popularity, first date added and the playlists it is in. Capped at limit rows (the header says how many match), so narrow the filters instead of asking for everything.

Args: filters: playlists, artist, album, genre (exact tag), genre_family, decade, year_from/to, popularity_min/max, added_from/to, duration_min/max (minutes), text (in the name). sort: popularity, year, added, duration, name or artist. Default order is descending (ascending for name and artist) unless ascending says otherwise. limit: rows to return (default 50, max 500). include_links: add each track's Spotify link (longer output).

Delete the local cache of the user's playlists. With also_log_out, delete the saved Spotify login too. Nothing on Spotify is changed.

Every track of a loaded playlist, in playlist order: track, artist (with featured artists), album, year, duration, popularity and date added. Reads the local cache, so it always has the full playlist.

Args: playlist: the playlist's name (or a unique part of it), ID or Spotify link. include_links: add each track's Spotify link (longer output).

Group the loaded tracks into a draft of new playlists, and open the draft dashboard.

Workflow: narrow the pool with filters, call with preview_only=true to see the counts, then run it. The draft is saved (ID like "d3") and nothing is written to Spotify. Tracks already organized ("done", see organize_progress) are left out unless include_done=true.

Args: mode: "category" (one group per decade and/or genre family) or "genres" (one group per chosen genre tag). "kmeans" (by audio similarity) comes with audio features, later. filters: playlists, decades and genre_families to narrow the pool before grouping. by: category mode only: "decade", "genre_family" or "both" (e.g. "Rock · 1990s"). A track in several families goes to the first one. Tracks without a genre or a release decade (when that dimension is used) are listed as unmatched, with the reason. genres: genres mode: exact genre tags to make groups for (a track with several chosen tags is in each group). If omitted, filters.genre_families picks every tag of those families; with neither, you get the list of genres in the pool (nothing is saved). also_by_decade: genres mode: also split each genre group by decade ("rock · 1980s"). include_done: include tracks already organized. preview_only: don't save a draft; return the pool counts and how many groups/unmatched.

The user's Spotify playlists: id, name, track count, whether they own it, its link, and whether it is already in the local cache ("current", "changed" since loading, or null).

Show the list to the user and ask which playlists they want to load before calling load_playlists.

Copy playlists from Spotify into the local cache and show the overview dashboard.

Only load the playlists the user chose. If they haven't said which ones, ask them first (list_my_playlists shows the options); don't load all of them unless they ask for that.

Args: playlists: playlist IDs or Spotify playlist links of the playlists the user chose. force: re-read playlists even if they haven't changed since the last load.

Playlists that haven't changed are skipped. The dashboard covers everything in the cache.

How much of the collection is organized: tracks already placed in a playlist built from a draft ("done", or skipped on purpose) or assigned to a group by hand ("manual") count toward the % of the library organized. Done tracks are left out of the next group_tracks. Reads the cache only.

DESTRUCTIVE for the user's organize progress: forgets which tracks are organized (done and manual), so every track is back in the pool and the % goes to 0. Only the progress is cleared: drafts, the cache and Spotify are untouched. Ask the user first; with confirm=false it only says what would be cleared.

Args: confirm: true only after the user agreed to clear their progress.

Show a draft of new playlists as a dashboard (Cluster Results): one card per group with its size, hours, top artists, genres and decades and sample tracks, the unmatched tracks with the reason, and the overall progress bar. The full track lists are on the web page it opens.

Args: draft: the draft ID ("d3"). Default: the latest one; the text lists the other drafts.

Show the overview dashboard of the loaded playlists again: KPIs, oldest/newest track, playlists, top artists, decades, popularity, albums, genres, additions over time and duplicates. load_playlists already shows it after loading.

Show the dashboard of one loaded playlist: header numbers, track highlights, averages, top artists, duplicates inside it, era by decade and year, top genres, growth over time and all its tracks. Opens in the user's browser (and inside the chat where the app supports it).

Args: playlist: the playlist's name (or a unique part of it), ID or Spotify link.

Take one or more playlists out of the local cache, so they leave the analysis, and show the overview of what remains. Nothing changes on Spotify: the playlists stay in the user's account and load_playlists brings them back.

Tracks and artists that no other loaded playlist has leave the cache too, and leave any draft that had them.

Args: playlists: names (or a unique part of the name), IDs or Spotify links of loaded playlists.