· 2 observations
Technical updates · 1
Package or technical metadata updated
View technical comparison →Spotify v4.3.0
Music and podcasts for you
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Recommend episodes with best film picks for the awards
Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 17, 2026.
From the marketplace listing
Explore a new way to discover music, podcasts and audiobooks, with recommendations picked just for you. Want music to power your next run, study session, or party? Just ask and Spotify will drop the right songs, artists or playlists into your conversation. With Spotify in ChatGPT you can: Ask for songs, artists, genres, or playlists and play them in Spotify. Find podcasts and audiobooks that match your interests. Spotify Premium listeners can describe a vibe and get a playlist made to match. Get recommendations based on your history right in your chat.
Language: English · Automatically detected from descriptions.
From the developer.
Exact text from the indicated source. A mention alone does not establish support for your task.
Spotify
Explore a new way to discover music, podcasts and audiobooks, with recommendations picked just for you. Want music to power your next run, study session, or party? Just ask and Spotify will drop the right songs, artists or playlists into your conversation. With Spotify in ChatGPT you can: Ask for songs, artists, genres, or playlists and play them in Spotify. Find podcasts and audiobooks that match your interests. Spotify Premium listeners can describe a vibe and get a playlist made to match. Get recommendations based on your history right in your chat.
· 2 observations
Package or technical metadata updated
View technical comparison →· 1 observation
Package or technical metadata updated
View technical comparison →· 1 observation
Package or technical metadata updated
View technical comparison →· 1 observation
Package or technical metadata updated
View technical comparison →· 3 observations
Is template instance added: “false”. App-68de829bf7648191acd70a907364c67c updated; open the comparison for details. App-68de829bf7648191acd70a907364c67c runtime updated; open the comparison for details. Spotify updated; open the comparison for details. 10 more changes in the comparison.
View comparison →Is template instance added: “false”. App-68de829bf7648191acd70a907364c67c updated; open the comparison for details. Spotify updated; open the comparison for details. Default prompt changed from “Recommend episodes with best film pics for the awards” to “Recommend episodes with best film picks for the awards”. 8 more...
View comparison →Package or technical metadata updated
View technical comparison →· 1 observation
Package or technical metadata updated
View technical comparison →Similar plugins could not be prepared right now. Please try again in a moment.
Browse plugins →--- name: browse-collections description: Look inside Spotify content you already have a URI for. Use when the user asks what tracks are on a playlist or album, which episodes a podcast has, the chapters of an audiobook, or details about specific items already shown in the chat, or when a generated playlist's tracks are needed. Covers get_entity (metadata for up to 20 URIs) and get_collection_items (paginated contents, with polling for playlists still being generated). Do not use to discover content from text; use search for that. --- # Browse playlists, albums, shows, and items Explicit user instructions take priority over this guidance. ## Pick the tool | Need | Tool | | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | Metadata for items you hold URIs for (name, creators, availability, library state) | `get_entity` | | The tracks, episodes, or chapters inside a playlist, album, podcast, or audiobook | `get_collection_items` | | Finding content from a name or description | `search` or `query_catalog` (see [search-spotify](../search-spotify/SKILL.md)) | You don't need the contents to share or play a collection. Its link works as soon as you have it. ## get_entity - `uris`: up to 20 Spotify URIs per call, from earlier results or pasted by the user. Never construct URIs. - `language`: the user's BCP 47 locale (`en-US`, `sv-SE`, `pt-BR`). Required. - Entities come back in request order. URIs that couldn't be resolved are listed in `unresolved` with a reason; tell the user those weren't found rather than dropping them silently. - Works signed out for public content; signed in adds availability and library status. ## get_collection_items - `uri`: a playlist, album, or show (podcast or audiobook) URI. - `page_size`: default 10, max 60. Ask for only what you need. - Pagination: pass `pagination.next_cursor` as `cursor` for the next page. With a cursor, omit `page_size` or repeat the first page's exact value; a different value is rejected. - `total_items` counts items before availability filtering and may be absent for dynamic playlists. Don't promise an exact count from it. - Podcasts usually list newest episodes first. ## Status and polling Check `status` before using the contents: | `status` | Action | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `READY` | Contents are complete. | | `GENERATION_IN_PROGRESS` | A generated playlist is still being assembled. Retry with the same `uri` and pagination arguments at most 5 times, waiting 2, 4, 8, 16, then 30 seconds. If it's still pending, stop, share the playlist link, and tell the user the tracks aren't ready yet. Retry later only if they ask. | | `FAILED` | Stop polling and tell the user the contents couldn
Preview of the first 4,000 characters. Read full instructions →
---
name: build-playlists
description: Creates and edits Spotify playlists. Use when the user explicitly asks to create, make, or generate a playlist, build one from songs discussed in the chat, or add, remove, rename, redescribe, or make collaborative an existing playlist. Excludes recommendations only, finding existing playlists, saving someone else's playlist, and audiobooks in playlists.
---
# Build and edit playlists
Explicit user instructions take priority over this guidance.
## Confirm intent first
- Only create a playlist when the user clearly asks for one. "Suggest workout songs" or "find me a party playlist" is a search, not a creation (see [search-spotify](../search-spotify/SKILL.md)).
- Hypothetical or tentative asks ("I might want a playlist...") wait until the user confirms.
- If the request has no detail ("make me a playlist"), ask for a mood, genre, activity, or artists before calling anything.
- `generate_playlist` builds music playlists only. For a playlist of specific podcast episodes, use `create_playlist` + `add_playlist_items` with the episode URIs.
- Audiobooks can't be added to playlists (only tracks and episodes can). Offer to save the audiobook instead.
## Pick the path
| Situation | Path |
| ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| User describes a vibe, theme, activity, or artists and wants Spotify to choose tracks | `generate_playlist` |
| User wants specific tracks: a list they gave, songs from earlier in the chat, a tracklist from a file | `create_playlist`, then `add_playlist_items` |
| `generate_playlist` didn't produce a playlist (see below) | `search` for tracks, then `create_playlist` + `add_playlist_items`, if the user agrees |
## generate_playlist
- `prompt` must start with the creation intent ("Create a...", "Make a..."). Add it if the user's wording lacks it.
- Keep the user's original language and context words ("my", "by", "from"). Replace private user identifiers with "me"/"my"; preserve artist, author, narrator, and content names exactly. Merge multi-turn context into one request. Convert durations to minutes. Do not add constraints the user didn't ask for.
- `language`: the user's BCP 47 locale. Required.
- The playlist is private to the user.
- Requires a signed-in user with Spotify Premium. If the response carries `NOT_SUBSCRIBED` or the explanation `PREMIUM_REQUIRED_FALLBACK`, no playlist was created. Tell the user that generating playlists from a description needs Spotify Premium, and offer to build one from search results with `create_playlist` and `add_playlist_items` instead.
- Tracks are assembled after the call returns. The playlist link is valid right away; share it. To read the tracks, call `get_collection_items` on the playlist URI and follow its polling rules (see [browse-collections](../browse-collections/SKILL.md)).
## create_playlist + add_playlist_items
1. Resolve each track to a URI first with `search` or `query_catalog`. Never invent or guess URIs.
2. `create_playlist` with `name` (required), optional `description`, and `collaborative` (defaults to false). New playlists are private.
3. Check `result` is `APPLIED`, then take `entity.uri`.
4. `add_playlist_items` with `playlist_uri` and `uris` (tracks and episodes only, up to 100 per call; split larger lists). Items append to the end.
5. Check every `add_playlist_items` response. On failure, stop and tell the user which batches were added and which failed; don't describe a partially populated playlist as complete.
6. SPreview of the first 4,000 characters. Read full instructions →
---
name: manage-library
description: Save or remove Spotify content in the user's library. Use when the user explicitly asks to save, like, add to library, follow an artist, podcast, or someone else's playlist, or the reverse (unsave, unlike, remove, unfollow) for a track, album, playlist, artist, podcast show, episode, or audiobook. Do not use proactively, on behalf of third parties, or to add tracks to a playlist.
---
# Manage the user's library
Explicit user instructions take priority over this guidance.
## When to act
- Only call `save_to_library` or `remove_from_library` when the user explicitly asks. Never save things just because they were recommended or played.
- "Add this to my workout playlist" is a playlist edit, not a library save (see [build-playlists](../build-playlists/SKILL.md)).
- Following an artist or podcast is a save; unfollowing is a remove.
## Getting the URI
- Any valid Spotify URI works: one from an earlier tool result (`search`, `query_catalog`, `get_entity`, `get_collection_items`, `get_currently_playing`) or one the user pastes. Never construct or guess one.
- If you don't have it yet, find the item first, and confirm with the user if more than one result could match.
- Supported: `spotify:track:`, `spotify:album:`, `spotify:playlist:`, `spotify:artist:`, `spotify:show:` (podcasts and audiobooks), `spotify:episode:`.
- One URI per call. For several items, make one call per item.
- "Save this song" usually means the song just discussed: reuse that result's URI. Call `get_currently_playing` (now-playing) only when the user means what is playing now ("like what's playing", "save the song on right now"). If it's unclear which song they mean, ask.
## Before calling
If the entity already shows `library_status`, use it:
| `library_status` | Meaning |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| `SAVED` | Already saved; don't save again. Removable. |
| `NOT_SAVED` | Can be saved. |
| `NOT_SAVEABLE` | Don't call `save_to_library`. This also covers the user's own playlists, which are already in their library and can still be removed. |
| `PRE_SAVED` | Unreleased item the user pre-saved. Treat as saved. |
## After calling
- Success: `save_to_library` returns `library_status: SAVED`; `remove_from_library` returns `NOT_SAVED`. Confirm to the user by name, with the Spotify link.
- If `library_status` is absent, the call failed. Never claim success.
| Error | Action |
| ------------------ | ------------------------------------------------------------ |
| `NOT_SAVEABLE` | Don't retry. Tell the user Spotify can't save this item. |
| `INVALID_ARGUMENT` | The URI was wrong. Re-find the item, then retry once. |
| `RATE_LIMITED` | Wait a moment, then retry once. |
| `INTERNAL_ERROR` | Retry once; if it fails again, tell the user it didn't work. |
---
name: now-playing
description: Tell the user what is playing on their Spotify right now. Use only when the user directly asks what song, track, episode, or audiobook is currently playing on Spotify, or explicitly refers to what is playing now. Not for "this song" when a song was just discussed in the chat. Do not call proactively, and do not use for play, pause, skip, or other playback control, which is not available.
---
# What's playing now
Explicit user instructions take priority over this guidance.
## When to call
- Call `get_currently_playing` (no arguments) only when the user asks what is playing, or explicitly refers to what is playing now ("save the song on right now"). For "save this song" or "more like this", reuse the item discussed in the conversation; ask if the reference is ambiguous.
- Don't call it proactively or to start a conversation.
- Play, pause, skip, queue, and volume aren't supported. Say so, and point the user to the Spotify app.
## Using the result
- Attribute playback to Spotify: "This is playing on Spotify: ...". Include the item's Spotify link.
- If nothing is playing, say there's no active Spotify playback right now.
- For follow-ups, reuse the returned entity's URI:
- "Save this" → `save_to_library` (see [manage-library](../manage-library/SKILL.md)).
- "More like this" → `search` with a prompt such as "more like <track> by <artist>" (see [search-spotify](../search-spotify/SKILL.md)).
## Errors
| Error | Action |
| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| `LICENSOR_RESTRICTED` | Something is playing, but it can't be shown. Say the current content can't be displayed. |
| `DEVICE_UNAVAILABLE` | No active Spotify device. Suggest opening Spotify and starting playback. |
| `CONTENT_NOT_PLAYABLE`, `CONTENT_NOT_AVAILABLE`, `NOT_ELIGIBLE` | Say the current item isn't available to show. Don't retry. |
| `UNKNOWN_ERROR` | Retry once, then say something went wrong. |
---
name: search-spotify
description: Finds and recommends Spotify music, podcasts, and audiobooks. Use for discovery, mood or activity requests, "more like X", known-title lookups, finding existing playlists, listening history, and saved-content queries. Excludes playlist creation or editing, library mutations, current-playback identification, lyrics, concerts, artist bios, and music news.
---
# Find music, podcasts, and audiobooks
Explicit user instructions take priority over this guidance.
## Pick the tool
| Request | Tool |
| ------------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
| Mood, vibe, activity, genre, "something like X", recommendations | `search` |
| Listening history, recently played, top artists, Liked Songs, "my playlists" | `search` (personalized when signed in) |
| Vague or partial memories ("that song from the Barbie movie") | `search` |
| Known titles with trusted values, e.g. a list of albums with artists and years | `query_catalog` |
| Several known items at once ("these 6 albums") | `query_catalog`, one call with up to 10 `queries` |
| You already hold Spotify URIs | `get_entity` (see [browse-collections](../browse-collections/SKILL.md)) |
When unsure, use `search`. A `search` call on a known title is never wrong; `query_catalog` on a mood or description returns nothing useful.
## Calling search
- `prompt`: pass the user's wording as-is, in their original language. Do not translate or reduce it to keywords.
- Allowed rewrites only (plus adding "audiobook" for audiobook requests, see below):
- Replace private user identifiers (the user's own name, usernames) with "me" or "my". Preserve artist, author, narrator, and content names exactly.
- Merge multi-turn context into one self-contained request. Prefer one search for "a + b + c" over three searches.
- Convert durations to minutes ("2 hours" becomes "120 minutes").
- `language`: the user's BCP 47 locale (`en-US`, `sv-SE`, `pt-BR`). Required.
- Expect at most 5 results per call, whatever `limit` says. To show more variety, run a second, differently-phrased search rather than raising `limit`.
- Personalization is automatic when the user is signed in. Do not add phrases like "based on my taste" unless the user said them.
## Calling query_catalog
- One object per item: `query` is the title or name, plus optional `creator` (artist, publisher, author, or narrator), `year` (`"1977"` or `"1975-1980"`), and `entity_types` (`MUSIC`, `TALK`, `BOOK`, `COLLECTION`, `CREATOR`).
- Results come back as one group per query, in input order. Read each group's `entities`, `warnings`, and `error` on their own.
- If some groups failed temporarily, keep the successful ones and retry only the failed queries.
- If a group is empty and the input might be conversational or misremembered, retry that item with `search`.
## Audiobooks
- Treat book requests ("listen to a book", "an audiobook for my commute", "books by Brandon Sanderson") as audiobook searches. Say "audiobook" in the `search` prompt so results lean toward books rather than podcasts about the book.
- Known title: `query_catalog` with the title in `query`, `entity_types: ["BOOK"]`, and the author or narrator in `creator` if known.
- Author- or narrator-only requests ("books by Brandon Sanderson"): use `search`. `query_catalog` matches titles, so an author name alone can miss their books.
- Audiobooks use `spotify:show:` URIs, Preview of the first 4,000 characters. Read full instructions →
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 17, 2026.
plugin_asdk_app_68de829bf7648191acd70a907364c67c
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.