Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_to_playlist

Add tracks or episodes to a playlist with playlist ID and URIs. Supports up to 100 items per call, optional position, and duplicate check.

Instructions

Add tracks or episodes to a playlist. Max 100 URIs per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urisYesTrack or episode URIs to add
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
positionNoInsert at index; appends if omitted
playlist_idYesPlaylist ID
check_duplicatesNoSkip URIs that are already in the playlist instead of appending them (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / check_duplicates
      Added value: +{
+  "description": "Skip URIs that are already in the playlist instead of appending them (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
    • addedInput schema / properties / position / maximum
      Added value: +9007199254740991
  2. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden but only reveals the 100-URI cap, which is already encoded in the schema as uris.maxItems. It does not state that duplicates are appended by default, that the operation mutates the playlist irreversibly, or what dry_run and position imply behaviorally, nor does it mention any returned snapshot or receipt.

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?

Two short sentences with no filler, and the hard constraint is front-loaded. It is efficient and readable, though it borders on under-specification given the 5-parameter surface.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters, no annotations, and no output schema, yet sits among closely related siblings (batch_add_to_playlist, add_to_queue, playlist_add_by_search). The description does not cover what the call returns, how it differs from batch_add_to_playlist, or the default duplicate-appending behavior, leaving the agent to infer too much for confident invocation.

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 baseline of 3 applies. The description's 'Max 100 URIs per call' reinforces the uris.maxItems constraint but adds no meaning beyond what the schema already documents for each parameter.

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 action ('Add') with a clear resource ('tracks or episodes to a playlist') and a cardinality constraint ('Max 100 URIs per call'). The action and resource are unambiguous, but it does not differentiate from the very similar sibling batch_add_to_playlist, 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?

The description provides no guidance on when to use this tool versus nearby alternatives such as batch_add_to_playlist, add_to_queue, or playlist_add_by_search. The 'Max 100 URIs per call' line is an operational constraint, not a selection criterion, and nothing excludes or routes to alternatives.

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