Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_playlist_cover

Read-onlyIdempotent

Retrieve the cover image URLs for a Spotify playlist by providing the playlist ID, returning results in a concise, detailed, or raw JSON format.

Instructions

Get a playlist's cover image URLs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for playlist_id, matching get_playlist
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

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. Changed6 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Alias for playlist_id, matching get_playlist",
+  "type": "string"
+}
    • 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"
+}
    • changedInput schema / properties / playlist_id / description
      Previous value: -"Playlist ID"New value: +"Playlist ID (or pass it as 'id')"
    • 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: -[
-  "playlist_id"
-]
  3. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile, and the description is fully consistent with them (no contradiction). The description adds only the small detail that 'URLs' is plural, hinting that multiple image sizes may be returned. It does not disclose return shape, auth requirements, or rate limits, but with annotations carrying the safety burden, a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single focused sentence with zero filler, front-loaded with the verb and resource. It is efficiently sized for a simple getter, though the brevity could have been leveraged to add sibling differentiation or usage context without becoming verbose.

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?

For a simple read-only getter with 100% schema coverage and safety annotations, the description is largely adequate. Gaps remain: no description of the return format despite the response_format parameter, and no routing between cover-related siblings (upload/clone/compare). The schema's note that 'id' matches get_playlist partially compensates by linking to a sibling's id format.

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 all four parameters (id, playlist_id, max_results, response_format) are already documented in the schema. The description adds nothing about parameters, so the baseline 3 applies. Notably, the schema's max_results and response_format parameters suggest the tool may behave more richly than the one-line description implies, but the schema itself documents them adequately.

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 ('Get') and resource ('a playlist's cover image'), and specifies the output ('URLs'). This distinguishes it from siblings like upload_playlist_cover, clone_playlist_cover, and compare_playlist_covers via the action verb. However, it doesn't explicitly name those alternatives, so differentiation is implied rather than stated.

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?

No guidance is provided on when to use this tool versus alternatives. The description never mentions the cover-related siblings (upload/clone/compare) or any condition that would select this tool over them. An agent must infer usage entirely from the tool name and the verb in the description.

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