Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

copy_playlist

Duplicate any Spotify playlist into a new one, preserving the original track order. Use dry-run to preview the new playlist before creating it.

Instructions

Duplicate an existing playlist into a new playlist, preserving track order. Creates the new playlist then adds tracks in batches of 100. Dry-run reports what would be created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoSource page size, 1–100. Default: 100
publicNoPublic flag for the new playlist. Default: false
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
new_nameYesName for the new playlist
scan_capNoMaximum source rows to scan; bounded by SPOTIFY_MCP_FETCH_ALL_CAP
descriptionNoDescription for the new playlist (defaults to source description)
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
collaborativeNoCollaborative flag. Default: false
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
source_playlist_idYesSource playlist ID, spotify:playlist: URI, or URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / scan_cap
      Added value: +{
+  "description": "Maximum source rows to scan; bounded by SPOTIFY_MCP_FETCH_ALL_CAP",
+  "maximum": 10000,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / source_playlist_id / description
      Previous value: -"Source playlist ID or spotify:playlist: URI"New value: +"Source playlist ID, spotify:playlist: URI, or URL"
    • addedInput schema / properties / source_playlist_id / minLength
      Added value: +1
  2. Addedv1.26.1

TDQS

A3.5/5.0
Behavior4/5

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

The only annotation is destructiveHint=false, so the description carries the burden of behavioral disclosure. It adds valuable transparency by stating that the tool creates the new playlist first, adds tracks in batches of 100, and supports a dry-run mode that reports what would be created. It does not cover rate limits, auth requirements, or failure modes, but the core behavior is well disclosed.

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 three sentences with no filler. The first sentence states the purpose, the second explains the workflow, and the third covers the dry-run behavior. Every sentence earns its place and the key information is front-loaded.

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 tool has 10 parameters and no output schema, and the description explains the main workflow well. However, it does not cover return values, response formats, or edge cases such as the interaction between limit, scan_cap, and max_results. It is adequate for a basic understanding but leaves gaps for a complex tool.

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 fully documented. The description reinforces the 'batches of 100' behavior which relates to the limit parameter and mentions dry-run, but it does not add meaning beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the verb 'Duplicate' and the resource 'existing playlist' into a new playlist, and adds a meaningful detail: preserving track order. It is specific enough to understand the tool's core function, but it does not explicitly disambiguate from sibling tools like clone_playlist_live or playlist_clone_snapshot.

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 given on when to use this tool versus alternatives such as clone_playlist_live or playlist_clone_snapshot. The description implies usage for duplicating a playlist, but provides no exclusions, prerequisites, or distinguishing conditions.

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