Search, discover, and play music and podcasts on Spotify. Returns up to 5 results, which can be a mix of tracks, artists, albums, podcasts, public playlists, and user-owned private playlists. Supports the following capabilities:
Capabilities: Entity search — Find tracks, artists, albums, playlists, podcast shows, or episodes by name or metadata (genre, decade, topic, etc.). Complex music queries — Generate playlists for moods, vibes, activities, genres, or multi-facet queries (e.g. “trap workout mix”, “90s alternative pop”). Recommendations — Get personalized recommendations for tracks, artists, albums, playlists, or podcasts based on the user’s taste. Similar content — Find artists, tracks, albums, or podcasts similar to a specific entity (e.g. “artists similar to Erykah Badu”). Context-aware suggestions — Suggest content based on what is currently playing (e.g. “more like this”, “play something similar”). Listening history — Retrieve recently played content, most-played items, or get recommendations based on listening history. User library — Access liked songs, saved shows/episodes, followed artists, and user playlists. Podcast discovery — Find podcasts by genre, topic, guest, popularity, or recency. Find specific episodes by order, number, date, or popularity. Albums & tracks by artist — Get an artist’s discography or tracks, optionally sorted by recency or popularity.
When to use: User wants to find, play, discover, or get recommendations for any music or podcast content. User describes a mood, vibe, activity, or genre rather than a specific entity. User asks about their listening history, recently played, most-played, or saved content. User asks "what have I been listening to", "my recent songs", "my top artists", etc.
Do NOT use when: Audiobooks — “You can’t search audiobooks on Spotify yet. Try the Spotify app.” Concerts, tour dates, podcast/song creation, podcast playlists, lyrics, bios, transcripts — “You can access this in the Spotify app.” Unsupported podcast queries: duration filtering, multi-entity similarity, long-lookback history. User wants facts/news about music. When the user explicitly asks or very clearly implies the intent to create a playlist, use the create_playlist tool instead.
Query rules: Pass the user's query through as-is. Only make very specific changes to the query for these particular scenarios:
- Replace all usernames/PII with "me"/"my" — never send real names or identifiers.
- Resolve multi-turn context into one self-contained request. (i.e. usually better to search once for a+b+c than one search per a, b, c, even if a,b,c is given separately)
- Convert durations to minutes (e.g., "2 hours" → "120 minutes").
- Language: The prompt MUST match the "language" parameter. Set "language" from user's input language first, then keep the prompt in that language. EN/FR/IT/DE/ES/PT → send as-is. Other languages → translate to English. When translating, keep all names of songs, artists, albums, playlists, and genres exactly as written.
Critical response rules: Always include Spotify links with every track/podcast/playlist/album/artist/ you present and/or recommend. Never fabricate or alter entity names, metadata, or links. This tool is read-only — it does not save, add, follow, or modify anything. Never claim content was added to the user's library or any action was performed. Do not generate lyrics, transcripts, biographies, or external content.