Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

compare_playlist_covers

Read-onlyIdempotent

Compare two Spotify playlist covers to check if their image URLs match and inspect dimensions.

Instructions

Compare two playlists covers: URL equality, dimensions. Quota: 2 GETs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoSource page size, 1–100. Default: 100
scan_capNoMaximum rows to read from each playlist; bounded by SPOTIFY_MCP_FETCH_ALL_CAP
playlist_aNoCanonical A playlist; provide with playlist_b
playlist_bNoCanonical B playlist; provide with playlist_a
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.0.1
    • changedInput schema / properties / playlist_a / description
      Previous value: -"Canonical A playlist; provide with playlist_b or one complete documented legacy pair"New value: +"Canonical A playlist; provide with playlist_b"
    • changedInput schema / properties / playlist_b / description
      Previous value: -"Canonical B playlist; provide with playlist_a or one complete documented legacy pair"New value: +"Canonical B playlist; provide with playlist_a"
    • removedInput schema / properties / playlist_id_a
      Removed value: -{
-  "description": "Deprecated one-release alias supported through v2.0; removed in v2.1. Provide a complete pair or canonical playlist_a/playlist_b.",
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / playlist_id_b
      Removed value: -{
-  "description": "Deprecated one-release alias supported through v2.0; removed in v2.1. Provide a complete pair or canonical playlist_a/playlist_b.",
-  "minLength": 1,
-  "type": "string"
-}
  2. Changed11 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Source page size, 1–100. Default: 100",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / playlist_a
      Added value: +{
+  "description": "Canonical A playlist; provide with playlist_b or one complete documented legacy pair",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / playlist_b
      Added value: +{
+  "description": "Canonical B playlist; provide with playlist_a or one complete documented legacy pair",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / playlist_id_a / description
      Added value: +"Deprecated one-release alias supported through v2.0; removed in v2.1. Provide a complete pair or canonical playlist_a/playlist_b."
    • addedInput schema / properties / playlist_id_a / minLength
      Added value: +1
    • addedInput schema / properties / playlist_id_b / description
      Added value: +"Deprecated one-release alias supported through v2.0; removed in v2.1. Provide a complete pair or canonical playlist_a/playlist_b."
    • addedInput schema / properties / playlist_id_b / minLength
      Added value: +1
    • addedInput schema / properties / scan_cap
      Added value: +{
+  "description": "Maximum rows to read from each playlist; bounded by SPOTIFY_MCP_FETCH_ALL_CAP",
+  "maximum": 10000,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / required
      Removed value: -[
-  "playlist_id_a",
-  "playlist_id_b"
-]
  3. Addedv1.26.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already carry readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuine value beyond that by disclosing the cost ('Quota: 2 GETs') and the shape of the comparison (URL equality plus dimensions), which an agent cannot read off the annotations.

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-loaded with the action and resource, with the cost disclosure appended. Nothing is wasted and speed of scanning is high.

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 no output schema and six parameters, the description carries return-shape duty and does hint at it (URL equality, dimensions). It omits edge cases such as missing covers or mismatched sizes, but for a read-only comparison tool this is close to complete.

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 six parameters (limit, scan_cap, playlist_a/b, max_results, response_format) are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('compare two playlists covers') and narrows the scope to URL equality and dimension checks, which separates it from one-cover tools like get_playlist_cover and clone_playlist_cover. It never names a sibling explicitly, so it stops short of a 5.

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?

There is no statement of when to reach for this versus get_playlist_cover or clone_playlist_cover, nor any precondition (e.g. both playlists must exist / have covers). The purpose is inferable but the selection guidance is absent.

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