Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Playlist Tracks

get_playlist_tracks

Read-onlyIdempotent

Retrieve tracks from a Spotify playlist with pagination controls, returning item details, total count, limit, and offset so you can fetch specific track ranges or all tracks safely.

Instructions

Get tracks from a playlist with full pagination support.

Args:
    playlist_id: Playlist ID
    limit: Max tracks to return (None for all tracks, up to 10,000 safety limit)
    offset: Number of tracks to skip for pagination (default 0)

Returns:
    PlaylistTracks with 'items' (list of tracks), 'total', 'limit', 'offset'

Note: Large playlists require pagination. Use limit/offset to get specific ranges:
- Get first 100: limit=100, offset=0
- Get next 100: limit=100, offset=100
- Get all tracks: limit=None (use with caution on very large playlists)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "playlist_id": "<playlist_id>"
    },
    "name": "get_playlist_tracks"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`items`	Yes
`limit`	No
`total`	Yes
`offset`	Yes
`returned`	Yes

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 tracks from a single playlist."

addedOutput schema / properties

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

addedOutput schema / required

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

changedOutput schema / title

Previous value: -"get_playlist_tracksDictOutput"New value: +"PlaylistTracks"

Addedv1.0.0Jan 2, 2026

TDQS

A4.2/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 adds genuinely new behavior: a 10,000-item safety cap when limit is None, and the pagination model of successive limit/offset windows. It does not describe auth requirements for private playlists, which is the main remaining gap.

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

Conciseness4/5

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

The purpose is front-loaded in one sentence and the pagination examples are actionable. The Returns block partially duplicates the existing output schema, which is mild waste, but the Args block earns its place because the schema has no parameter descriptions.

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 3-parameter read tool with annotations and an output schema already in place, the description covers purpose, parameter semantics, pagination strategy, and the safety limit. Only edge-case behavior (invalid or inaccessible playlist_id, error responses) is unaddressed, which is minor given the output schema handles return shape.

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?

Schema description coverage is 0%, so the description carries the full burden and does so: it explains that limit=None means all tracks subject to a 10,000 safety limit, that offset is the number of tracks to skip with default 0, and gives worked pagination examples. This is meaning the schema alone does not convey.

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?

The first sentence gives a specific verb and resource ("Get tracks from a playlist") plus a scope qualifier ("with full pagination support"), which clearly separates it from metadata tools like get_playlist. It never names a sibling tool explicitly, so differentiation is implied rather than stated.

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 Note section gives concrete when-to-use guidance: large playlists require pagination, use limit/offset for ranges, and use limit=None with caution on very large playlists. It lacks explicit routing to alternatives (e.g., get_playlist for metadata vs this tool for track listings), but the operational context is clear.

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

Deploy Server