Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

find_duplicate_saved_tracks

Read-onlyIdempotent

Detect duplicate saved Spotify tracks by matching ISRC, album, and duration, optionally flagging near duplicates for review. Cross-reference groups with a playlist and never change your library.

Instructions

Read-only duplicate detection over your saved (liked) tracks. Exact groups require the same non-null ISRC and album id with duration within ±2s, and keep the oldest dated save. On opt-in, near-duplicate groups show same-title/artist tracks whose ISRC, release, or duration differs; these are distinct saved tracks and are review-only with no removals. Undated saves sort after dated saves. Optionally pass a playlist_id to cross-reference which group members also appear in that playlist. Never mutates your library.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
playlist_idNoOptional playlist ID to cross-reference: members of each duplicate group that also appear in this playlist are flagged, so cleanup or review decisions can account for where the track is already curated.
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
include_near_duplicatesNoAlso report same-title/artist groups with a different ISRC, release, or duration. Near duplicates are review-only and never recommend removal. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / include_near_duplicates / description
      Previous value: -"Also report same-song groups whose durations differ by more than ±2s (remasters/re-recordings). Default false."New value: +"Also report same-title/artist groups with a different ISRC, release, or duration. Near duplicates are review-only and never recommend removal. Default false."
    • changedInput schema / properties / playlist_id / description
      Previous value: -"Optional playlist ID to cross-reference: members of each duplicate group that also appear in this playlist are flagged, so removal decisions can account for where the track is already curated."New value: +"Optional playlist ID to cross-reference: members of each duplicate group that also appear in this playlist are flagged, so cleanup or review decisions can account for where the track is already curated."
  2. Addedv1.26.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the exact-match criteria (same non-null ISRC and album id, duration ±2s, keeps oldest dated save), that near-duplicates are review-only with no removals, that undated saves sort last, and that it never mutates the library.

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?

Front-loads the core purpose and then layers matching semantics efficiently; every sentence carries information. A few sentences are dense and could be tighter, but there is no filler.

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, the description carries the burden of explaining what comes back, and it does describe group types, exact vs. near distinction, and undated-save ordering. It stops short of describing the concise/detailed/json return shapes in depth, leaving a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds genuine meaning: playlist_id denotes cross-referencing group members against a playlist for cleanup decisions, and include_near_duplicates is framed as an opt-in review-only mode. These enrich the parameters beyond their schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Read-only duplicate detection over your saved (liked) tracks.' The 'saved (liked) tracks' scope cleanly distinguishes it from sibling playlist duplicate tools like find_duplicates_in_playlist and find_duplicate_tracks_across_playlists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear conditions for the two modes (exact groups vs. opt-in near duplicates) and explains the optional playlist_id cross-reference use case. It never explicitly names an alternative sibling or states when NOT to use it, so it stops short of full routing guidance.

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