← SpotifyCONTENT HISTORY

Update to Spotify

Snapshot Nov 18, 2026 · 18:11 UTC · version 4.4.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for build-playlists

Skill instructions — Now says: that the tool call succeeded (no JSON-RPC error and neither `isError` nor `is_error` is true), then take `entity.uri`. 6. Share the playlist link from the...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Spotify and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 24, 2026 · 12:49 UTC

`result` is `APPLIED`, then take `entity.uri`. 6. Share the playlist link from the `create_playlist` response. - If `can_edit_items` is false, don't try to edit; tell the user they can't edit this playlist. If it is absent (common for co...

After

Nov 18, 2026 · 18:11 UTC

that the tool call succeeded (no JSON-RPC error and neither `isError` nor `is_error` is true), then take `entity.uri`. 6. Share the playlist link from the `create_playlist` response. The new playlist is not in the user's library (`librar...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -36,14 +36,14 @@
 
 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`.
+3. Check that the tool call succeeded (no JSON-RPC error and neither `isError` nor `is_error` is true), 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. Share the playlist link from the `create_playlist` response.
+6. Share the playlist link from the `create_playlist` response. The new playlist is not in the user's library (`library_status: NOT_SAVED`); only call `save_to_library` if the user asks to keep or save it.
 
 ## Editing an existing playlist
 
-- If `can_edit_items` is false, don't try to edit; tell the user they can't edit this playlist. If it is absent (common for collaborative playlists), editability is unknown: go ahead when the user asks, and rely on the tool's `NOT_PERMITTED` result.
+- If `can_edit_items` is false, don't try to edit; tell the user they can't edit this playlist. If it is absent (common for collaborative playlists), editability is unknown: go ahead when the user asks, and rely on the tool's `NOT_PERMITTED` error.
 - `add_playlist_items`: append tracks or episodes.
 - `remove_playlist_items`: removes every occurrence of each URI. Confirm with the user before removing items they did not name explicitly.
 - `update_playlist_details`: change `name`, `description`, or `collaborative`. Send at least one.
@@ -55,13 +55,16 @@
 
 ## Reading the result
 
-All edit tools return `result`:
+On success, edit tools return MCP `isError: false`; `create_playlist` also returns the created playlist in `entity`. On failure, they return `isError: true`, `is_error: true` and the reason in `error.error_code`:
 
-| `result`        | Meaning                                               | Action                                                                                                                                                                                                                                                                                   |
-| --------------- | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `APPLIED`       | Done                                                  | Confirm to the user with the playlist link                                                                                                                                                                                                                                               |
-| `NOT_FOUND`     | Playlist doesn't exist                                | Re-check the URI; don't retry blindly                                                                                                                                                                                                                                                    |
-| `NOT_PERMITTED` | User can't edit it                                    | Tell the user; offer to create their own copy                                                                                                                                                                                                                                            |
-| `CHANGE_FAILED` | Unexpected failure; the change may still have applied | Don't retry `create_playlist` or `add_playlist_items`, which would duplicate the playlist or its tracks. Tell the user it may not have worked and offer to check the playlist with `get_collection_items`. `remove_playlist_items` and `update_playlist_details` are safe to retry once. |
+| Outcome                                     | Meaning                                                               | Action                                                                                                                                                                                                                                                                                   |
+| ------------------------------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Successful tool response                    | Done                                                                  | Confirm to the user with the playlist link                                                                                                                                                                                                                                               |
+| `NOT_FOUND`                                 | Playlist doesn't exist                                                | Re-check the URI; don't retry blindly                                                                                                                                                                                                                                                    |
+| `NOT_PERMITTED`                             | User can't edit it                                                    | Tell the user; offer to create their own copy                                                                                                                                                                                                                                            |
+| `CHANGE_FAILED`, `BACKEND_ERROR`, `TIMEOUT` | Unexpected failure; the change may still have applied                 | Don't retry `create_playlist` or `add_playlist_items`, which would duplicate the playlist or its tracks. Tell the user it may not have worked and offer to check the playlist with `get_collection_items`. `remove_playlist_items` and `update_playlist_details` are safe to retry once. |
+| `INVALID_ARGUMENT`                          | A bad argument or a playlist limit; `error.message` names the problem | Fix the argument; don't retry the same call                                                                                                                                                                                                                                              |
+| `RATE_LIMITED`                              | Too many requests; nothing changed                                    | Wait a moment, then retry once                                                                                                                                                                                                                                                           |
+| `REQUEST_REJECTED`                          | The playlist service rejected the edit; nothing changed               | Tell the user; don't retry the same call                                                                                                                                                                                                                                                 |
 
-Never claim a change happened unless `result` is `APPLIED`.
+Only confirm a change after receiving a successful tool response. A JSON-RPC error, `isError: true`, `is_error: true`, or a missing response is not confirmation.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: build-playlists\ndescription: 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.\n---\n\n# Build and edit playlists\n\nExplicit user instructions take priority over this guidance.\n\n## Confirm intent first\n\n- 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)).\n- Hypothetical or tentative asks (\"I might want a playlist...\") wait until the user confirms.\n- If the request has no detail (\"make me a playlist\"), ask for a mood, genre, activity, or artists before calling anything.\n- `generate_playlist` builds music playlists only. For a playlist of specific podcast episodes, use `create_playlist` + `add_playlist_items` with the episode URIs.\n- Audiobooks can't be added to playlists (only tracks and episodes can). Offer to save the audiobook instead.\n\n## Pick the path\n\n| Situation                                                                                             | Path                                                                                   |\n| ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |\n| User describes a vibe, theme, activity, or artists and wants Spotify to choose tracks                 | `generate_playlist`                                                                    |\n| 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`                                           |\n| `generate_playlist` didn't produce a playlist (see below)                                             | `search` for tracks, then `create_playlist` + `add_playlist_items`, if the user agrees |\n\n## generate_playlist\n\n- `prompt` must start with the creation intent (\"Create a...\", \"Make a...\"). Add it if the user's wording lacks it.\n- 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.\n- `language`: the user's BCP 47 locale. Required.\n- The playlist is private to the user.\n- 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.\n- 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)).\n\n## create_playlist + add_playlist_items\n\n1. Resolve each track to a URI first with `search` or `query_catalog`. Never invent or guess URIs.\n2. `create_playlist` with `name` (required), optional `description`, and `collaborative` (defaults to false). New playlists are private.\n3. Check `result` is `APPLIED`, then take `entity.uri`.\n4. `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.\n5. 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.\n6. Share the playlist link from the `create_playlist` response.\n\n## Editing an existing playlist\n\n- If `can_edit_items` is false, don't try to edit; tell the user they can't edit this playlist. If it is absent (common for collaborative playlists), editability is unknown: go ahead when the user asks, and rely on the tool's `NOT_PERMITTED` result.\n- `add_playlist_items`: append tracks or episodes.\n- `remove_playlist_items`: removes every occurrence of each URI. Confirm with the user before removing items they did not name explicitly.\n- `update_playlist_details`: change `name`, `description`, or `collaborative`. Send at least one.\n\n## Handoffs\n\n- Tracks from an earlier search, query_catalog, or browse-collections result are already resolved: reuse their URIs instead of searching again.\n- \"Add what's playing to my playlist\": get the URI with `get_currently_playing` (now-playing), then `add_playlist_items`.\n\n## Reading the result\n\nAll edit tools return `result`:\n\n| `result`        | Meaning                                               | Action                                                                                                                                                                                                                                                                                   |\n| --------------- | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `APPLIED`       | Done                                                  | Confirm to the user with the playlist link                                                                                                                                                                                                                                               |\n| `NOT_FOUND`     | Playlist doesn't exist                                | Re-check the URI; don't retry blindly                                                                                                                                                                                                                                                    |\n| `NOT_PERMITTED` | User can't edit it                                    | Tell the user; offer to create their own copy                                                                                                                                                                                                                                            |\n| `CHANGE_FAILED` | Unexpected failure; the change may still have applied | Don't retry `create_playlist` or `add_playlist_items`, which would duplicate the playlist or its tracks. Tell the user it may not have worked and offer to check the playlist with `get_collection_items`. `remove_playlist_items` and `update_playlist_details` are safe to retry once. |\n\nNever claim a change happened unless `result` is `APPLIED`.\n"
AFTER
"---\nname: build-playlists\ndescription: 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.\n---\n\n# Build and edit playlists\n\nExplicit user instructions take priority over this guidance.\n\n## Confirm intent first\n\n- 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)).\n- Hypothetical or tentative asks (\"I might want a playlist...\") wait until the user confirms.\n- If the request has no detail (\"make me a playlist\"), ask for a mood, genre, activity, or artists before calling anything.\n- `generate_playlist` builds music playlists only. For a playlist of specific podcast episodes, use `create_playlist` + `add_playlist_items` with the episode URIs.\n- Audiobooks can't be added to playlists (only tracks and episodes can). Offer to save the audiobook instead.\n\n## Pick the path\n\n| Situation                                                                                             | Path                                                                                   |\n| ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |\n| User describes a vibe, theme, activity, or artists and wants Spotify to choose tracks                 | `generate_playlist`                                                                    |\n| 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`                                           |\n| `generate_playlist` didn't produce a playlist (see below)                                             | `search` for tracks, then `create_playlist` + `add_playlist_items`, if the user agrees |\n\n## generate_playlist\n\n- `prompt` must start with the creation intent (\"Create a...\", \"Make a...\"). Add it if the user's wording lacks it.\n- 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.\n- `language`: the user's BCP 47 locale. Required.\n- The playlist is private to the user.\n- 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.\n- 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)).\n\n## create_playlist + add_playlist_items\n\n1. Resolve each track to a URI first with `search` or `query_catalog`. Never invent or guess URIs.\n2. `create_playlist` with `name` (required), optional `description`, and `collaborative` (defaults to false). New playlists are private.\n3. Check that the tool call succeeded (no JSON-RPC error and neither `isError` nor `is_error` is true), then take `entity.uri`.\n4. `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.\n5. 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.\n6. Share the playlist link from the `create_playlist` response. The new playlist is not in the user's library (`library_status: NOT_SAVED`); only call `save_to_library` if the user asks to keep or save it.\n\n## Editing an existing playlist\n\n- If `can_edit_items` is false, don't try to edit; tell the user they can't edit this playlist. If it is absent (common for collaborative playlists), editability is unknown: go ahead when the user asks, and rely on the tool's `NOT_PERMITTED` error.\n- `add_playlist_items`: append tracks or episodes.\n- `remove_playlist_items`: removes every occurrence of each URI. Confirm with the user before removing items they did not name explicitly.\n- `update_playlist_details`: change `name`, `description`, or `collaborative`. Send at least one.\n\n## Handoffs\n\n- Tracks from an earlier search, query_catalog, or browse-collections result are already resolved: reuse their URIs instead of searching again.\n- \"Add what's playing to my playlist\": get the URI with `get_currently_playing` (now-playing), then `add_playlist_items`.\n\n## Reading the result\n\nOn success, edit tools return MCP `isError: false`; `create_playlist` also returns the created playlist in `entity`. On failure, they return `isError: true`, `is_error: true` and the reason in `error.error_code`:\n\n| Outcome                                     | Meaning                                                               | Action                                                                                                                                                                                                                                                                                   |\n| ------------------------------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Successful tool response                    | Done                                                                  | Confirm to the user with the playlist link                                                                                                                                                                                                                                               |\n| `NOT_FOUND`                                 | Playlist doesn't exist                                                | Re-check the URI; don't retry blindly                                                                                                                                                                                                                                                    |\n| `NOT_PERMITTED`                             | User can't edit it                                                    | Tell the user; offer to create their own copy                                                                                                                                                                                                                                            |\n| `CHANGE_FAILED`, `BACKEND_ERROR`, `TIMEOUT` | Unexpected failure; the change may still have applied                 | Don't retry `create_playlist` or `add_playlist_items`, which would duplicate the playlist or its tracks. Tell the user it may not have worked and offer to check the playlist with `get_collection_items`. `remove_playlist_items` and `update_playlist_details` are safe to retry once. |\n| `INVALID_ARGUMENT`                          | A bad argument or a playlist limit; `error.message` names the problem | Fix the argument; don't retry the same call                                                                                                                                                                                                                                              |\n| `RATE_LIMITED`                              | Too many requests; nothing changed                                    | Wait a moment, then retry once                                                                                                                                                                                                                                                           |\n| `REQUEST_REJECTED`                          | The playlist service rejected the edit; nothing changed               | Tell the user; don't retry the same call                                                                                                                                                                                                                                                 |\n\nOnly confirm a change after receiving a successful tool response. A JSON-RPC error, `isError: true`, `is_error: true`, or a missing response is not confirmation.\n"
Full snapshot data
{
  "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.",
  "included_files": [],
  "name": "build-playlists",
  "skill_md_contents": "---\nname: build-playlists\ndescription: 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.\n---\n\n# Build and edit playlists\n\nExplicit user instructions take priority over this guidance.\n\n## Confirm intent first\n\n- 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)).\n- Hypothetical or tentative asks (\"I might want a playlist...\") wait until the user confirms.\n- If the request has no detail (\"make me a playlist\"), ask for a mood, genre, activity, or artists before calling anything.\n- `generate_playlist` builds music playlists only. For a playlist of specific podcast episodes, use `create_playlist` + `add_playlist_items` with the episode URIs.\n- Audiobooks can't be added to playlists (only tracks and episodes can). Offer to save the audiobook instead.\n\n## Pick the path\n\n| Situation                                                                                             | Path                                                                                   |\n| ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |\n| User describes a vibe, theme, activity, or artists and wants Spotify to choose tracks                 | `generate_playlist`                                                                    |\n| 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`                                           |\n| `generate_playlist` didn't produce a playlist (see below)                                             | `search` for tracks, then `create_playlist` + `add_playlist_items`, if the user agrees |\n\n## generate_playlist\n\n- `prompt` must start with the creation intent (\"Create a...\", \"Make a...\"). Add it if the user's wording lacks it.\n- 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.\n- `language`: the user's BCP 47 locale. Required.\n- The playlist is private to the user.\n- 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.\n- 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)).\n\n## create_playlist + add_playlist_items\n\n1. Resolve each track to a URI first with `search` or `query_catalog`. Never invent or guess URIs.\n2. `create_playlist` with `name` (required), optional `description`, and `collaborative` (defaults to false). New playlists are private.\n3. Check that the tool call succeeded (no JSON-RPC error and neither `isError` nor `is_error` is true), then take `entity.uri`.\n4. `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.\n5. 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.\n6. Share the playlist link from the `create_playlist` response. The new playlist is not in the user's library (`library_status: NOT_SAVED`); only call `save_to_library` if the user asks to keep or save it.\n\n## Editing an existing playlist\n\n- If `can_edit_items` is false, don't try to edit; tell the user they can't edit this playlist. If it is absent (common for collaborative playlists), editability is unknown: go ahead when the user asks, and rely on the tool's `NOT_PERMITTED` error.\n- `add_playlist_items`: append tracks or episodes.\n- `remove_playlist_items`: removes every occurrence of each URI. Confirm with the user before removing items they did not name explicitly.\n- `update_playlist_details`: change `name`, `description`, or `collaborative`. Send at least one.\n\n## Handoffs\n\n- Tracks from an earlier search, query_catalog, or browse-collections result are already resolved: reuse their URIs instead of searching again.\n- \"Add what's playing to my playlist\": get the URI with `get_currently_playing` (now-playing), then `add_playlist_items`.\n\n## Reading the result\n\nOn success, edit tools return MCP `isError: false`; `create_playlist` also returns the created playlist in `entity`. On failure, they return `isError: true`, `is_error: true` and the reason in `error.error_code`:\n\n| Outcome                                     | Meaning                                                               | Action                                                                                                                                                                                                                                                                                   |\n| ------------------------------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Successful tool response                    | Done                                                                  | Confirm to the user with the playlist link                                                                                                                                                                                                                                               |\n| `NOT_FOUND`                                 | Playlist doesn't exist                                                | Re-check the URI; don't retry blindly                                                                                                                                                                                                                                                    |\n| `NOT_PERMITTED`                             | User can't edit it                                                    | Tell the user; offer to create their own copy                                                                                                                                                                                                                                            |\n| `CHANGE_FAILED`, `BACKEND_ERROR`, `TIMEOUT` | Unexpected failure; the change may still have applied                 | Don't retry `create_playlist` or `add_playlist_items`, which would duplicate the playlist or its tracks. Tell the user it may not have worked and offer to check the playlist with `get_collection_items`. `remove_playlist_items` and `update_playlist_details` are safe to retry once. |\n| `INVALID_ARGUMENT`                          | A bad argument or a playlist limit; `error.message` names the problem | Fix the argument; don't retry the same call                                                                                                                                                                                                                                              |\n| `RATE_LIMITED`                              | Too many requests; nothing changed                                    | Wait a moment, then retry once                                                                                                                                                                                                                                                           |\n| `REQUEST_REJECTED`                          | The playlist service rejected the edit; nothing changed               | Tell the user; don't retry the same call                                                                                                                                                                                                                                                 |\n\nOnly confirm a change after receiving a successful tool response. A JSON-RPC error, `isError: true`, `is_error: true`, or a missing response is not confirmation.\n"
}

SHA-256 of public snapshot: 7a7eb6a5225614e5bb362d73f0ff9088af04b17b1f8b470a26bdb6d6664f444e