Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_playlist

Export any Spotify playlist to an M3U playlist or CSV spreadsheet, capturing every track and podcast item for backup or offline use.

Instructions

Export a playlist's full item list as an M3U playlist file or a CSV spreadsheet. Pages every item; pass output_path to write a file (created with mode 0600) inside the configured output root, or omit it to get the document inline. CSV cells are formula-safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format: m3u (playable playlist) or csv (spreadsheet)m3u
overwriteNoAllow replacing an existing file at output_path (refused by default)
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
output_pathNoWrite the full document to this local file (relative paths resolve inside the output root, default ~/.spotify-mcp/exports) instead of returning it inline
playlist_idYesPlaylist ID
include_headersNoEmit the #EXTM3U marker / CSV header row
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.2
    • changedInput schema / properties / output_path / description
      Previous value: -"Write the full document to this local file instead of returning it inline"New value: +"Write the full document to this local file (relative paths resolve inside the output root, default ~/.spotify-mcp/exports) instead of returning it inline"
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Allow replacing an existing file at output_path (refused by default)",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.26.1

TDQS

A3.8/5.0
Behavior3/5

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

It adds genuinely useful behavioral detail beyond the annotations: internal pagination, mode 0600, output-root sandboxing, inline-vs-file behavior, and formula-safe CSV. However, the claim of a 'full item list' conflicts with the schema's max_results default of 50, so the transparency is incomplete and potentially misleading.

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?

Three dense sentences with the purpose front-loaded and no filler. Each sentence carries a distinct, useful fact: output formats, file-vs-inline behavior, and CSV security.

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 schema fills in most parameter detail and the description covers output modes well, but the description would mislead an agent about default truncation unless max_results is raised, and it does not mention sibling export formats. For a 7-parameter tool with no output schema, these are notable gaps.

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; the description adds value on top by explaining output_path semantics (mode 0600, relative to the output root, inline when omitted) and CSV cell safety. Repeating the other parameters would be redundant.

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 opens with a specific verb and resource: exporting a playlist's full item list to M3U or CSV. It is clearly distinct from a generic get/list tool, but it does not explicitly differentiate itself from sibling exports like export_playlist_json, export_playlist_markdown, or export_all_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?

The description gives clear guidance on choosing between file output and inline return ('pass output_path... or omit it') and explains the output root and file mode. It stops short of naming when not to use this tool, such as pointing agents to JSON or Markdown export siblings.

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