Last.fm Builders¶

Collect artists, albums, and tracks from Last.fm charts, tags, and listening history.

Choose a builder¶

Use collection_order: custom to preserve the returned order after matching and sync_mode: sync to keep membership synchronized. A collection contains one music level; set builder_level: album or builder_level: track for tag builders when needed. Those levels are already the defaults for album- and track-specific builders.

Shared options¶

Username-only forms for user top charts, loved tracks, and recent tracks use 50 results. User top charts also accept lists of usernames or dictionaries to combine charts. Replace placeholder usernames in the examples with real usernames.

Global charts¶

Pass a result limit directly, or as limit in a dictionary. This example selects up to 50 global top tracks; 50 is an integer count. Use lastfm_chart_top_artists to select artists instead, or dictionary form such as lastfm_chart_top_tracks: {limit: 50}.

collections:
  Global Top Tracks:
    lastfm_chart_top_tracks: 50
    collection_order: custom
    sync_mode: sync

Tag charts¶

lastfm_tag_charts accepts a tag string, such as dance, or a dictionary with tag and optional limit. A YAML list of tags or dictionaries combines results.

This example selects up to 50 Dance tracks. builder_level: track changes the default artist level, while tag: dance is the source tag string.

collections:
  Top Dance Tracks:
    builder_level: track
    lastfm_tag_charts:
      tag: dance
      limit: 50
    collection_order: custom
    sync_mode: sync

Personal tags¶

lastfm_user_tags requires both username and tag, with an optional limit. A YAML list of user/tag dictionaries combines sources.

Selects up to 50 albums this user has personally tagged favourites. This uses personal tags, rather than the global top chart for that tag. The collection's album level determines which type of tagged item Last.fm is asked for.

collections:
  My Tagged Albums:
    builder_level: album
    lastfm_user_tags:
      username: YOUR_LASTFM_USERNAME
      tag: favourites
      limit: 50
    sync_mode: sync

User top charts¶

Use lastfm_user_top_artists, lastfm_user_top_albums, or lastfm_user_top_tracks with a username or a dictionary of username, period, and limit. A username alone selects the overall top 50 at the corresponding music level.

collections:
  My Monthly Top Albums:
    lastfm_user_top_albums:
      username: YOUR_LASTFM_USERNAME
      period: 1month
      limit: 50
    collection_order: custom
    sync_mode: sync

collections:
  My Most Played Tracks:
    lastfm_user_top_tracks:
      username: YOUR_LASTFM_USERNAME
      period: overall
      limit: 50
    collection_order: custom
    sync_mode: sync

collections:
  Friends' Top Artists:
    lastfm_user_top_artists:
      - username: FIRST_LASTFM_USERNAME
        period: 1month
        limit: 25
      - username: SECOND_LASTFM_USERNAME
        period: overall
        limit: 25
    collection_order: custom
    sync_mode: sync

Loved tracks¶

Accepts a username or a dictionary with username and limit. This selects up to 50 loved-track results, newest loved first. The limit is counted before duplicate tracks are removed, so the resulting collection may contain fewer tracks.

collections:
  My Loved Tracks:
    lastfm_user_loved_tracks:
      username: YOUR_LASTFM_USERNAME
      limit: 50
    collection_order: custom
    sync_mode: sync

Recent tracks¶

Accepts a username or a dictionary with username, limit, and optional time bounds. Currently playing tracks are excluded. The limit counts completed scrobbles before deduplication; the remaining tracks retain newest-play-first order.

This example selects up to 50 scrobbles from January 2024 using numeric UTC Unix timestamps, rather than date strings. Duplicates are removed after selection.

collections:
  Tracks Played in January 2024:
    lastfm_user_recent_tracks:
      username: YOUR_LASTFM_USERNAME
      from: 1704067200
      to: 1706745599
      limit: 50
    collection_order: custom
    sync_mode: sync

Matching and missing items¶

Kometa tries MusicBrainz IDs first, then accepts unique name-based matches. Comparisons ignore case and treat typographic dashes like regular hyphens.

Artist matching does not require Lidarr. Fetching artist MusicBrainz IDs may require a separate API call per chart artist, so large limits take longer. Album name fallback also handles Last.fm release IDs versus Plex release-group IDs. Tag builders use these same music matching rules.

Ambiguous matches and items without enough information are skipped. With show_missing, unmatched items appear under Missing Artists from Library, Missing Albums from Library, or Missing Tracks from Library. With save_report, the library report includes missing artists with available MusicBrainz IDs, Albums Missing, and Tracks Missing. Ambiguous name matches are also marked in the log.