Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Liked Songs

get_saved_tracks

Read-onlyIdempotent

Retrieve your saved or liked tracks from Spotify's library. Supports pagination with limit and offset to browse through the full collection.

Instructions

Get user's saved/liked tracks (Liked Songs library).

Args:
    limit: Max tracks to return per page (1-50, default 20)
    offset: Number of tracks to skip for pagination (default 0)

Returns:
    SavedTracks with 'items' (tracks with added_at timestamp) and pagination info

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`next`	No
`items`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes
`previous`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.6.1Sep 17, 2026

addedOutput schema / $defs / Track / properties / id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / $defs / Track / properties / id / default
```
Added value: +null
```
removedOutput schema / $defs / Track / properties / id / type
```
Removed value: -"string"
```

addedOutput schema / $defs / Track / properties / is_local

Added value: +{
+  "default": false,
+  "title": "Is Local",
+  "type": "boolean"
+}

addedOutput schema / $defs / Track / properties / played_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Played At"
+}

changedOutput schema / $defs / Track / required

Previous value: -[
-  "name",
-  "id",
-  "artist"
-]New value: +[
+  "name",
+  "artist"
+]

Changed5 schema fields changedv0.3.1Jun 2, 2026

addedOutput schema / $defs

Added value: +{
+  "Track": {
+    "description": "A Spotify track with metadata.",
+    "properties": {
+      "added_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Added At"
+      },
+      "album": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Album"
+      },
+      "album_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Album Id"
+      },
+      "artist": {
+        "title": "Artist",
+        "type": "string"
+      },
+      "artists": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Artists"
+      },
+      "duration_ms": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Duration Ms"
+      },
+      "external_urls": {
+        "anyOf": [
+          {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "External Urls"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "popularity": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Popularity"
+      },
+      "release_date": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Release Date"
+      }
+    },
+    "required": [
+      "name",
+      "id",
+      "artist"
+    ],
+    "title": "Track",
+    "type": "object"
+  }
+}

addedOutput schema / description

Added value: +"Paginated saved/liked tracks."

addedOutput schema / properties

Added value: +{
+  "items": {
+    "items": {
+      "$ref": "#/$defs/Track"
+    },
+    "title": "Items",
+    "type": "array"
+  },
+  "limit": {
+    "title": "Limit",
+    "type": "integer"
+  },
+  "next": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Next"
+  },
+  "offset": {
+    "title": "Offset",
+    "type": "integer"
+  },
+  "previous": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Previous"
+  },
+  "total": {
+    "title": "Total",
+    "type": "integer"
+  }
+}

addedOutput schema / required

Added value: +[
+  "items",
+  "total",
+  "limit",
+  "offset"
+]

changedOutput schema / title

Previous value: -"get_saved_tracksDictOutput"New value: +"SavedTracks"

Addedv1.0.0Jan 2, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds useful behavioral detail not in the annotations, such as pagination behavior, the limit range, and that items include an added_at timestamp. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-structured: a one-sentence purpose followed by Args and Returns blocks. Every line conveys distinct information, with no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple paginated read operation with two optional parameters, the description covers purpose, parameter meaning, and return shape. Safety is already covered by annotations. It does not explicitly discuss authentication or alternative tools, but those are not critical gaps for this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no parameter descriptions (0% coverage), so the description must compensate. It fully does: limit is explained as 'Max tracks to return per page (1-50, default 20)' and offset as 'Number of tracks to skip for pagination (default 0)'—adding range, defaults, and semantics beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Get user's saved/liked tracks (Liked Songs library)', naming a specific verb and resource. This clearly distinguishes it from sibling mutation tools like save_tracks and remove_saved_tracks, and from other retrieval tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description identifies the exact use case—fetching the user's Liked Songs library—so an agent can infer when to call it. It does not explicitly name alternative tools or exclusions, but the resource label is unambiguous and the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.