Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

taste_to_playlist

Generate a playlist track list from a stats.fm user's taste profile, blending lifetime top tracks with recent streams. Preview with dry_run; read-only, never writes to Spotify.

Instructions

Taste profile → playlist track list (DRY RUN first): blend lifetime tops with recent streams into a copy-pasteable track list. Read-only — never writes to Spotify.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoBlend seed. Default: mixed
dry_runNoPreview only (default true). False still only returns the list — writes happen via Spotify tools.
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
track_countNoTracks to list. Default: 20
statsfm_userYesstats.fm user ID (or username) — public profile, no auth needed
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.30.0

TDQS

A4.4/5.0
Behavior5/5

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

Explicitly discloses that the tool never writes to Spotify and is read-only. Also labels it a 'DRY RUN,' so users know there will be no side effects.

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?

The description is two short sentences, direct and free of fluff. It efficiently communicates purpose and safety.

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?

The description covers the core purpose and read-only behavior. While it doesn't detail output formats, the 'copy-pasteable track list' hint and schema cover the essentials.

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 description doesn't add parameter-specific details, but the schema already covers all 6 parameters with 100% description coverage, so the baseline is appropriate.

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 description clearly states the tool's function: blending lifetime tops with recent streams into a track list. It also explicitly notes the read-only nature, making the purpose unambiguous.

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?

Provides direct guidance with 'DRY RUN first' and 'Read-only — never writes to Spotify,' telling users the tool is safe to preview. Doesn't reference alternatives, but the dry-run instruction is a strong usage hint.

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