yit-player
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| search_music_on_youtubeA | Searches YouTube for music or songs based on a natural language query. If play_first_result is true, it immediately starts playing the best match. |
| play_search_resultA | Plays a specific track number from the most recent search results. Only call this AFTER a successful search. |
| pause_musicA | Pauses the currently playing track. |
| resume_musicB | Resumes playing the currently paused track. |
| stop_musicA | Stops music playback entirely and closes the player. |
| skip_to_next_trackB | Skips to the next track in the queue. |
| play_previous_trackB | Goes back to the previously played track. |
| loop_current_trackB | Locks the player to loop the current track indefinitely. |
| stop_loopingA | Stops looping the current track so playback proceeds normally. |
| get_player_statusA | Gets the current playback status (Playing/Paused/Stopped) and the name of the current track. |
| get_current_queueA | Returns the list of tracks currently in the playback queue. |
| add_to_queueB | Appends a track number from the latest search results directly to the end of the queue. |
| clear_queueA | Clears all upcoming tracks from the queue except the one currently playing. |
| list_favoritesA | Lists all the user's saved favorite tracks. |
| play_favoritesB | Plays the user's favorite tracks. If index_to_play is not provided, plays all favorites. If an index is provided, plays only that specific favorite. |
| add_currently_playing_to_favoritesB | Adds the currently playing music track to the user's favorites list. |
| add_search_result_to_favoritesA | Adds a specific track number from the recent search results to favorites. |
| remove_favoriteB | Removes a track from favorites using its index number from the favorites list. |
| get_listening_profileA | Returns what Yit has learned about the user's music taste as JSON: top artists and tracks (recency-weighted, from songs they actually finished), what they play at this time of day, recently played, often skipped, recent searches, favorites and dislikes. Call this before choosing music for vague or mood-based requests. |
| dj_play_for_meA | Builds and plays a personal queue from the user's taste: favourites they haven't heard recently, mixed with new songs similar to what they love (via YouTube Mix). discovery = share of new-to-them songs (0 to 1). |
| play_songsA | Plays a hand-picked list of specific songs in order. Each item should be a precise search like "Artist - Song Title". Set replace_queue=false to append after the current queue instead. |
| start_radioA | Plays an endless-style radio of songs similar to a seed (song name or YouTube URL). With no seed it continues from the currently playing song, or from the user's top track if nothing is playing. |
| like_current_songA | Marks the currently playing song as liked (adds to favorites and boosts it in future recommendations). |
| dislike_current_songA | Marks the current song as disliked so it's never recommended again, and skips it. block_artist=true also excludes that artist from all future recommendations. |
| import_youtube_music_historyA | Imports the user's Google Takeout YouTube watch history (watch-history.json or .html) so Yit knows their taste from day one. By default only YouTube Music entries are imported. |
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 25 tools
Most playback, queue, and favorites operations are distinct, but there is notable overlap between add_currently_playing_to_favorites and like_current_song, since both add the current track to favorites while like_current_song also boosts recommendations. Multiple playback entry points (search-and-play, play_favorites, dj_play_for_me, start_radio, play_songs) are differentiated by descriptions but still require careful selection.
Tool names are consistently snake_case and mostly follow a verb_noun pattern. Minor deviations exist, such as dj_play_for_me, skip_to_next_track versus play_previous_track, and some longer multi-preposition names like add_currently_playing_to_favorites.
At 25 tools, the surface is on the heavy side for a music player, even one with personalization and history import. Some operations could likely be consolidated, especially favorites/like handling and playback-initiation variants.
Core music-player workflows are covered: search, playback control, queue management, favorites, listening profile, radio/DJ modes, and history import. Minor gaps remain around volume/seek controls, removing or reordering specific queue items, and broader playlist management.