Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_playlist_items

Retrieve tracks and episodes from a Spotify playlist with pagination, response field filtering, market availability relinking, and fetch-all support.

Instructions

List a playlist's items on a single page. Use market to relink tracks and flag unavailable ones, and fields/additional_types to trim the payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for playlist_id, matching get_playlist
limitNoItems per page, 1–100. Default: 100
fieldsNoComma-separated list of response fields to keep, e.g. 'total,items(track(name,uri))'
marketNoISO 3166-1 alpha-2 country code, e.g. 'GB'; relinks tracks to that market and flags unavailable ones
offsetNoPagination offset. Default: 0
fetch_allNoFetch every item across pages (up to 500), continuing FROM offset rather than restarting at 0. limit is the page size. Note: library tools' fetch_all instead ignores offset — contracts differ between modules (#110).
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
playlist_idNoPlaylist ID (or pass it as 'id')
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
additional_typesNoItem types to include beyond the default 'track', e.g. ['track', 'episode']

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.28.0
    • addedInput schema / properties / fetch_all
      Added value: +{
+  "description": "Fetch every item across pages (up to 500), continuing FROM offset rather than restarting at 0. limit is the page size. Note: library tools' fetch_all instead ignores offset — contracts differ between modules (#110).",
+  "type": "boolean"
+}
  2. Addedv1.26.1

TDQS

C2.9/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 burden. It discloses that market relinks tracks and flags unavailable ones, but it does not mention pagination behavior, default limits, max_results semantics, response format options, or error conditions. For a read tool this is a notable gap.

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?

Two sentences with zero filler: the primary action is front-loaded, and the second sentence efficiently groups the optional parameters by their shared purpose. Every word earns its place.

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

Completeness2/5

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

The tool has 10 parameters, no annotations, and no output schema, yet the description omits key runtime behavior such as fetch_all pagination contracts, max_results defaults, response_format handling, and how 'single page' interacts with limit/offset. It is adequate as a stub but not complete for correct invocation.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description adds moderate value by explaining market's relinking/unavailable-flagging behavior and that fields/additional_types trim the payload, which slightly enriches the schemas. It does not comment on other parameters, but they are already well documented in the schema.

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 description states a specific verb and resource ('List a playlist's items') and clarifies the single-page scope, which distinguishes it from get_playlist (metadata) and pagination-related siblings. It does not explicitly name a sibling it is not, but the 'single page' phrasing adds useful specificity.

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 gives parameter-level guidance (use market to relink, fields/additional_types to trim) but provides no tool-level when-to-use guidance or alternatives. Given the long sibling list, an agent is not told why to choose this over get_playlist, search_within_playlist, or export_playlist.

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

Deploy Server

Other Tools