Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_playlist_items

Read-onlyIdempotent

Retrieve a Spotify playlist's tracks and episodes with pagination, market relinking, and field filtering.

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. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
+}
  3. Addedv1.26.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already mark this as read-only and idempotent, so the safety profile is covered. The description adds real behavioral context about single-page listing and market-based relinking/flagging, but it does not disclose pagination behavior beyond the single-page claim and says nothing about the return shape or how fetch_all interacts with the stated single-page behavior.

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 tight sentences front-load the core behavior and then immediately point to the most decision-relevant parameters. Every clause earns its place, with no filler or redundant restatement of the schema.

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?

The schema is exhaustive and annotations cover safety, so the description does not need to repeat everything. Still, with no output schema and a 10-parameter tool, the description leaves the fetch_all behavior and return format unmentioned, and 'single page' could mislead an agent into ignoring the built-in multi-page fetch option.

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 schema already thoroughly documents market, fields, additional_types, fetch_all, and the rest. The description essentially restates what market, fields, and additional_types do without adding new meaning, so it neither hurts nor materially improves parameter understanding.

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 clearly states the verb ('List') and resource ('a playlist's items'), and adds the scope 'on a single page' which helps set boundaries. It is not as strong as it could be because it never names a sibling like get_playlist to explicitly differentiate, 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 Guidelines3/5

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

The description gives useful parameter-level guidance ('Use market to relink tracks and flag unavailable ones, and fields/additional_types to trim the payload'), implying when options matter. However, it never states when to choose this over nearby alternatives like get_playlist, get_playlist_followers, or playlist_snapshot, and it omits mention of fetch_all despite saying 'a single page'.

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