Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

get_playlist_items

Retrieve tracks or episodes from a Spotify playlist by ID, with options for limit, offset, and market to page through its contents.

Instructions

Get items (tracks/episodes) in a playlist.

    Args:
        playlist_id: The Spotify ID of the playlist.
        limit: Maximum number of items to return (1-50, default 20).
        offset: Index of the first item to return (default 0).
        market: ISO 3166-1 alpha-2 country code.

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Jun 9, 2026

addedInput schema / properties / market

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

First observedv0.1.1May 5, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the parameter list. It does not state that this is a read-only operation, whether authentication is required, how pagination terminates (total count), or rate-limit behavior. The limit/offset hints at paging but no actual behavioral trait is described.

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?

Front-loaded purpose sentence followed by a clean per-argument list. It is appropriately sized with minimal waste, though the Args block is somewhat boilerplate.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. For a simple read tool with no annotations, the description covers all four parameters but omits usage context and any behavioral disclosure, leaving it only minimally adequate.

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 compensate and it does: it defines playlist_id as a Spotify ID, gives limit's range (1-50) and default (20), offsets default (0), and market as an ISO 3166-1 alpha-2 country code. This adds real meaning the schema lacks, though it omits how market affects track availability/relinking.

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 (Get) and resource (items in a playlist) and clarifies that items are tracks/episodes, which distinguishes it from the sibling get_playlist. It does not explicitly name or contrast any alternative tool, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

The description never says when to use this tool versus alternatives like get_playlist, get_track, or search. There are no conditions, prerequisites, or exclusions given, leaving usage entirely to inference.

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