Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

import_playlist

Parse M3U or CSV documents and append their Spotify URIs to a target playlist, skipping tracks already present. Preview with dry_run before writing.

Instructions

Parse an M3U or CSV document (the inverse of export_playlist) and append its Spotify URIs to a target playlist. Pass the document inline via content, or read it from input_path (a regular file inside the configured read roots). URIs already in the playlist are skipped, so a re-run adds nothing. Adds in batches of 100. Use dry_run=true to preview without writing. Result records the document source and the use made of it (consent_note); under 100 new URIs nothing is gated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoDocument format; auto-detected when omitted
contentNoThe M3U or CSV document body, passed inline
dry_runNoParse and report what would be added without touching the playlist
input_pathNoRead the document from this local file instead of content
playlist_idYesTarget playlist ID, spotify:playlist: URI, or share URL
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / playlist_id / description
      Previous value: -"Target playlist ID or spotify:playlist: URI"New value: +"Target playlist ID, spotify:playlist: URI, or share URL"
  2. Changed1 schema field changedv1.28.0
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  3. Addedv1.26.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the lone destructiveHint=false annotation: discloses idempotent dedup (existing URIs skipped, re-run adds nothing), 100-URI batching, dry_run semantics, and consent_note gating behavior under 100 new URIs. This is exactly the write-safety context an agent needs for a mutation tool.

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?

Front-loads the core action, then packs input modes, idempotency, batching, preview, and gating into tight sentences with no filler. Every clause carries operational value.

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?

No output schema, and the description proactively notes the result records the document source and consent_note, plus the gating threshold. Complete for a mutation tool; only failure/error behavior for malformed documents is unaddressed.

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 real meaning: input_path must be a regular file inside the configured read roots, and content is the inline alternative. It also frames dry_run as preview-only, beyond the schema's terse wording.

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 ('parse... and append') plus resource (M3U/CSV document into a target playlist) and explicitly positions itself as the inverse of export_playlist, so an agent can distinguish it from sibling importers and exporters.

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?

Explains the two input modes (inline content vs input_path from read roots) and when to use dry_run=true to preview, plus the sibling relationship to export_playlist. No explicit 'when-not' or alternative-tool routing, but the context is clear.

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