Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

playlist_symmetric_difference

Find tracks that appear in exactly one of two Spotify playlists, excluding shared songs, to compare playlists and identify unique additions or missing tracks.

Instructions

Tracks in exactly one of two playlists (XOR). 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

B3.3/5.0
Behavior3/5

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

The annotation destructiveHint=false already signals a non-destructive read operation. The description adds a useful behavioral detail beyond the annotation: 'Quota: 2 GETs', which tells the agent about cost before invocation. It does not cover auth requirements, pagination behavior, or output structure, so it is adequate but still thin for a playlist-comparison operation.

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?

Extremely concise and front-loaded: the operation is stated first, then the quota cost. Both sentences carry information that an agent can use, and there is no filler or repetition.

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 description states the core operation and a quota cost, which is enough to invoke the tool against a fully documented schema. However, with no output schema and no return-format guidance, it leaves gaps around what the returned result looks like, ordering, pagination behavior, and how the two playlist inputs are expected to pair. It is minimally complete rather than fully self-contained.

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%, with all six parameters documented in the input schema, including defaults, bounds, and response_format enum values. The description adds no parameter-level syntax or semantics beyond what the schema already provides, so the baseline of 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 the specific operation as 'Tracks in exactly one of two playlists (XOR)', which is a clear symmetric-difference result set over playlist track resources. The XOR qualifier distinguishes it from intersection-style siblings like overlap_playlists and union-style siblings like playlist_union. It stops short of naming an explicit action verb or routing alternatives, but the purpose is unmistakable.

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 when-to-use guidance, no exclusions, and no explicit alternatives. An agent must infer that this tool is appropriate only for symmetric-difference comparisons from the operation itself. There is no mention of related siblings such as playlist_subtract, playlist_union, or overlap_playlists.

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