mcp-spotify

by obrien-matthew

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_playlist_tracks

Retrieve tracks from any Spotify playlist with pagination support. Returns track names, artists, IDs, and total count.

Instructions

Get the tracks in a Spotify playlist.

Supports pagination via limit (max 100) and offset. Returns track names, artists, IDs, and total count.

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 29, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Describes return values (track names, artists, IDs, total count) but no annotations exist. Missing details on authentication needed, rate limits, or that it's a read-only operation.

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?

Four sentences, zero wasted words. Essential information front-loaded.

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?

With 3 parameters and no output schema, it covers core functionality (pagination, returned fields). Minor missing details: exact return format or error handling, but adequate for basic use.

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 coverage is 0%; description compensates fully by explaining limit (max 100) and offset for pagination, and clarifies playlist_id is required. Adds meaning beyond the 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?

Clearly states 'Get the tracks in a Spotify playlist' – a specific verb and resource. Distinguishes from sibling tools like get_album_tracks, get_saved_tracks, etc.

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?

Mentions pagination via limit and offset, but no explicit when-to-use vs alternatives or when-not-to-use. Does not compare to search or retrieval siblings.

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