Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

export_playlists

Export readable Spotify playlists and Liked Songs to CSV files enriched with album, year, ISRC, genres, and available tempo/key data, then return the file paths and a summary.

Instructions

Export all readable playlists (plus Liked Songs) to CSV files enriched with album, year, ISRC, genres and, where Spotify still allows, tempo/key. Writes tracks.csv + playlists.csv and returns their paths and a summary. Can take minutes for large libraries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
enrichNoFetch genres + audio features (default true)
out_dirNoFolder to write to (default ~/Downloads/spotify-export-<date>)
include_likedNoInclude Liked Songs (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does a solid job: it names the on-disk side effects (two named CSV files plus default output location), the return value (file paths and a summary), and a latency warning. It also flags a graceful degradation condition ('where Spotify still allows, tempo/key'), which is valuable behavioral context. Gaps remain around overwrite behavior for existing files and failure handling for unreadable playlists.

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 tight sentences, front-loaded with the action and output, followed by return value and the runtime caveat. Every clause carries information; nothing is padding.

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?

For a three-optional-parameter tool with no output schema and no annotations, the description covers what is produced, where it lands, what is returned, and how long it can take. Only edge-case behavior (existing files, partial failures, auth requirements) is left unstated.

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, and the description adds genuine meaning on top: 'plus Liked Songs' explains include_liked, and the enrichment list of album/year/ISRC/genres/tempo/key clarifies what enrich actually toggles. It does not address out_dir behavior, but the added value above schema text is real.

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 and resource ('Export all readable playlists (plus Liked Songs)') and the concrete artifact produced ('CSV files enriched with album, year, ISRC, genres...'), naming the exact files tracks.csv + playlists.csv. That level of specificity makes it immediately distinguishable from read-only siblings like list_playlists or playlist_tracks, which retrieve rather than write files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The use case is implied clearly enough (bulk CSV export of a library), and the note that it 'can take minutes for large libraries' helps an agent decide when to avoid it. However, there is no explicit when-to-use framing, no named alternative such as list_playlists for lightweight inspection, and no prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.