Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Liked Songs

get_saved_tracks

Read-onlyIdempotent

Retrieve a user's saved or liked Spotify tracks with limit and offset pagination to browse their Liked Songs library page by page.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_saved_tracks"
  }
}

Input Schema

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

Output 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.

Changed3 schema fields changedv0.8.1Nov 4, 2026

addedOutput schema / $defs / Track / properties / show

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

addedOutput schema / $defs / Track / properties / show_id

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

addedOutput schema / $defs / Track / properties / type

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

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description still adds genuinely new behavioral facts: the per-page ceiling of 1-50 (absent from the schema, which has no min/max), the default page size, the offset-based pagination model, and the fact that each returned track carries an added_at timestamp.

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?

Purpose is front-loaded in one line, then Args and Returns in a compact docstring layout with no filler. Every line carries information an agent can act on.

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 two-parameter paginated read with an output schema, this covers params, page bounds, and return shape adequately, and annotations cover safety. Minor gaps: it does not state that "user" means the authenticated user (auth requirement) or whether an empty library returns an empty items array.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does: both parameters get meaning (max per page, tracks to skip) plus the undocumented 1-50 range and both defaults. It stops short of explaining what happens when offset exceeds the library size or how to detect the last page.

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

Purpose4/5

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

States a specific verb and resource ("Get user's saved/liked tracks") and pins the scope with "(Liked Songs library)", which separates it in spirit from get_tracks and get_playlist_tracks. It never names a sibling explicitly, so the differentiation is implied by the scope phrase rather than spelled out.

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

Usage Guidelines3/5

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

The "Liked Songs library" framing implies when this is the right tool, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as get_tracks, check_saved_tracks, or save_tracks/remove_saved_tracks among the 44 siblings. Usage is inferable but not guided.

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

Deploy Server