Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_all_playlists

Export all Spotify playlists with track items to JSON or CSV files for backup or migration. Choose owned or all playlists and specify output directory.

Instructions

Export every owned (or all) playlist with metadata + items to a sidecar file. Quota: GET /me/playlists + N×GET /playlists/{id}/items; capped by fetchAllCap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoowned = only playlists you ownall
formatNoOutput formatjson
output_dirNoLocal directory to write into, confined to the output root (default ~/.spotify-mcp/portability, set SPOTIFY_MCP_PORTABILITY_DIR to move it)
include_itemsNoInclude track items per playlist
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.2
    • changedInput schema / properties / output_dir / description
      Previous value: -"Local directory (default: ~/.spotify-mcp/portability)"New value: +"Local directory to write into, confined to the output root (default ~/.spotify-mcp/portability, set SPOTIFY_MCP_PORTABILITY_DIR to move it)"
  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

A4.2/5.0
Behavior4/5

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

destructiveHint=false is already in annotations, and the description adds meaningful behavioral detail with the quota formula: GET /me/playlists + N×GET /playlists/{id}/items, capped by fetchAllCap. This helps the agent reason about cost and batch size, though auth requirements and sidecar-file naming are not 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?

Two short, dense sentences front-load the core action and then add the quota constraint without any filler or repetition. Every sentence earns its place.

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?

Given five fully documented parameters, the description covers the operation, scope choice, output format, output directory, and quota behavior. Minor ambiguity remains around the exact meaning of 'all' and the shape of the returned result, but with no output schema and strong parameter docs this is a minor gap.

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?

The input schema has 100% description coverage: all five parameters already carry descriptions, defaults, and enums. The description adds tool-level context like sidecar output and quota, but does not materially refine individual parameter meaning beyond what the schema already provides.

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?

The phrase 'Export every owned (or all) playlist with metadata + items to a sidecar file' names a specific verb, resource, and scope. The qualifier 'every' and the sidecar-file output clearly distinguish it from singular or JSON-specific export siblings, even though no sibling is named.

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 context for the intended use case: bulk export of owned/all playlists, with scope selectable via the schema. It stops short of explicitly naming alternatives like export_playlist or sidecar_export_bundle or stating when not to use this tool, so the routing is left partly to inference.

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