Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_playlist

Retrieve a Spotify playlist's metadata, cover image, and items with pagination and fetch-all options.

Instructions

Get a playlist's metadata (including cover image) and items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for playlist_id
limitNoItems per page, 1–100. Default: 50
offsetNoPagination offset for items. Default: 0
fetch_allNoFetch all items across pages (up to 500), continuing FROM offset. limit is the page size. Note: library tools' fetch_all ignores offset — contracts differ between modules (#110).
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
playlist_idNoPlaylist ID
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / fetch_all / description
      Previous value: -"Fetch all items across pages (up to 500) instead of a single page"New value: +"Fetch all items across pages (up to 500), continuing FROM offset. limit is the page size. Note: library tools' fetch_all ignores offset — contracts differ between modules (#110)."
    • changedInput schema / properties / id / description
      Previous value: -"Playlist ID"New value: +"Alias for playlist_id"
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Max items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)",
+  "exclusiveMinimum": 0,
+  "maximum": 2000,
+  "type": "integer"
+}
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / playlist_id
      Added value: +{
+  "description": "Playlist ID",
+  "type": "string"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "id"
-]
  2. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states that the tool retrieves metadata and items. It does not disclose pagination behavior, default result size, the fetch_all limitation ('continuing FROM offset'), the difference between limit and max_results, or that response_format changes the output shape. The word 'Get' implies a read, but key behavioral traits are left to the schema.

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 a single efficient sentence that front-loads the verb and resource and includes the most distinctive extra detail (cover image) without wasted words. It is appropriately sized for a simple read tool, though not rich in context.

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?

Despite the tool having seven parameters, no output schema, and a large sibling set, the description offers only 'metadata' and 'items' as the expected result. It does not explain what metadata fields appear, how pagination affects the result, or how the identifier aliases relate, leaving an agent under-informed for a reliable 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 description coverage is 100%, so the parameters are already well documented in structured form; the description adds no parameter-level meaning beyond naming the playlist. Baseline 3 is appropriate because the schema carries the heavy lifting and the description does not need to compensate.

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 names a specific verb and resource ('Get a playlist's metadata') and usefully specifies that it includes the cover image and items, which distinguishes it at a glance from item-only or cover-only siblings such as get_playlist_items and get_playlist_cover. It does not explicitly name those alternatives or define the exact scope of 'metadata', so it falls just short of full differentiation.

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 no guidance about when to choose this tool over siblings like get_playlist_items, get_playlist_cover, or get_playlist_snapshot, and does not mention that id or playlist_id must be supplied despite zero required parameters in the schema. Usage context is left entirely to inference.

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