Spotify MCP Server

by jamiew

Overview Schema Source Related Servers Discussions Admin

Python

Local

List My Playlists

list_playlists

Read-onlyIdempotent

Fetch the current user's Spotify playlists page by page using limit and offset for complete library access.

Instructions

Get current user's playlists with pagination support.

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

Returns:
    PlaylistList with 'items' (list of playlists) and pagination info ('total', 'limit', 'offset')

Note: For users with many playlists, use offset to paginate through results.
Example: offset=0 gets playlists 1-20, offset=20 gets playlists 21-40, etc.

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.

Addedv0.6.1Sep 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds value by explaining pagination behavior (limit/offset), the return shape (PlaylistList with items and pagination info), and a concrete example. This goes beyond the annotations and clarifies expected behavior without contradicting them.

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 well-structured with labeled Args, Returns, and Note sections. It starts with the purpose, provides essential details, and includes a helpful example without any fluff. Every sentence contributes to understanding or usage.

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

Completeness5/5

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

For a simple read-only list tool, the description is complete. It covers both parameters, explains pagination, and references the output schema. Annotations handle safety and side-effect disclosures. No critical information an agent needs to call the tool correctly is missing.

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 is the sole source of parameter meaning. It fully compensates by explaining limit (1-50, default 20) and offset (default 0) with clear semantics and an example. This adds significant meaning beyond the bare schema types and defaults.

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 states a specific verb and resource: 'Get current user's playlists with pagination support.' This clearly distinguishes it from siblings like get_playlist (singular, specific playlist) and create_playlist, making the purpose unambiguous.

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 description gives clear context that this tool lists the current user's playlists, and the pagination note explains how to handle large result sets. However, it does not explicitly mention when to use this tool versus alternatives like get_playlist for a single playlist or search_music for non-owned playlists. Usage guidance is implied but not explicit.

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