lastfm-taste-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LASTFM_API_KEY | Yes | Your Last.fm API key (required). Tool calls return "LASTFM_API_KEY is not set" if missing. | |
| LASTFM_USERNAME | No | Default user for the `user_*` tools, used when the agent doesn't name one. This is the name in your profile URL (last.fm/user/<name>). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| user_get_infoB | Profile overview: total scrobbles, number of artists/tracks/albums, country and signup date. |
| user_get_recent_tracksA | Individual plays with timestamps, newest first, optionally within a date range. Use for "what did I listen to on Tuesday", listening times, or counting plays yourself. |
| user_get_top_tracksA | The user's most played tracks in a time window (their personal favourites), with play counts. Not the same as artist_get_top_tracks (an artist's popular songs) or tag_get_top_tracks (songs with a tag). |
| user_get_top_artistsA | The user's most played artists in a time window, with play counts. |
| user_get_top_albumsB | The user's most played albums in a time window, with play counts. |
| user_get_loved_tracksB | Tracks the user marked as loved (hearted) on Last.fm, newest first, with the date loved. |
| user_get_top_tagsA | Tags the user has applied themselves on Last.fm, by how often they used them. This is NOT the genre/mood of their music; for that use track_get_top_tags or artist_get_top_tags. |
| user_get_personal_tagsA | Items the user personally tagged with a given tag (see user_get_top_tags for their tags). |
| user_get_weekly_chart_listA | Which past weeks have charts, newest first, with the from/to values needed by the user_get_weekly_*_chart tools. Use it to compare specific weeks. |
| user_get_weekly_track_chartB | The user's track chart for one specific week (most recent by default), with play counts. |
| user_get_weekly_artist_chartA | The user's artist chart for one specific week (most recent by default), with play counts. |
| user_get_weekly_album_chartA | The user's album chart for one specific week (most recent by default), with play counts. |
| user_get_friendsA | The user's Last.fm friends. Their usernames can be passed to the other user_* tools. |
| track_get_top_tagsA | Genre/mood tags listeners gave a track (e.g. chill, sad, rock), strongest first; count is relative weight 0-100. Single tracks are often untagged; fall back to artist_get_top_tags. |
| artist_get_top_tagsA | Genre/mood tags listeners gave an artist, strongest first; count is relative weight 0-100. |
| album_get_top_tagsB | Genre/mood tags listeners gave an album, strongest first; count is relative weight 0-100. |
| track_get_infoB | Details for one track: album, length, global popularity, top tags, and how many times the user played it and whether they loved it. |
| track_get_similarA | Tracks similar to one track (good for "more like this"), with a 0-1 similarity score. |
| artist_get_similarB | Artists similar to one artist, with a 0-1 similarity score. |
| artist_get_top_tracksA | An artist's most popular tracks across all Last.fm listeners (not the user's plays). |
| tag_get_infoB | What a tag means: short description and how widely it is used. |
| tag_get_similarA | Tags related to a tag (e.g. chill → chillout, downtempo). Last.fm often returns nothing here. |
| tag_get_top_tracksA | The most popular tracks carrying a tag across all listeners (good for mood/genre requests and discovering new songs). Not the user's own plays. |
| tag_get_top_artistsA | The most popular artists carrying a tag across all listeners. Not the user's own plays. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
The tool set has many similar-sounding families (user_get_top_tracks, artist_get_top_tracks, tag_get_top_tracks; user_get_top_tags vs track/artist/album_get_top_tags), but descriptions explicitly distinguish scopes. A few weekly/top/list variants could still be misselected by a hurried agent, so it is mostly but not perfectly distinct.
Names consistently follow an entity_action_object snake_case pattern, such as user_get_recent_tracks, track_get_similar, and tag_get_top_artists. Minor structural variation in user_get_weekly_chart_list does not break the predictable convention.
Twenty-four tools is on the heavy side, but the Last.fm taste domain spans users, tracks, artists, albums, tags, weekly charts, and similarity relationships. Each tool maps to a distinct read operation, so the count is reasonable though slightly over-scoped.
The surface covers core taste workflows: user stats, recent/top/loved tracks, weekly charts, friends, personal tags, similar tracks/artists, tag discovery, and track info. Minor gaps like artist_get_info or album_get_info exist, but they are not critical dead ends for the stated taste-analysis purpose.