Spotify custom mcp server - Manage playlists, search content, and follow users/artists
Single tool ('search') with adequate but incomplete definition. Tool has a proper verb-noun name and accepts structured input with correct enum constraints. However, the response handling is severely broken: the function returns an empty dict or error strings rather than structured Spotify results. The description is present but generic, lacking specific guidance on when to use this tool or what to expect. Parameter descriptions exist but lack examples of expected query formats. No output schema is documented, forcing the LLM to guess result structure. Error handling returns bare error messages without recovery guidance. The implementation (app/core/search.py line ~45) filters results but never populates the 'results' dict, meaning successful calls return {}. This is a critical functional defect that makes the tool unusable.
Search Spotify for albums, artist, playlist, tracks, shows, episodes, or audiobooks. - q: Basic search query string. - search_type: A list of search types to look for (album, artist, playlist, track, show, episode, audiobook).
Critical: search tool returns empty dict on success. Line ~45 in app/core/search.py creates results={} and checks if data['artists'] exists but never populates results. Function always returns {} for valid API responses.
Missing output schema documentation. Tool description does not specify what fields the LLM should expect in the response (artist names, URLs, popularity scores, etc.). LLM cannot plan downstream calls or extract relevant data.
Error responses lack recovery guidance. HTTPStatusError returns raw status code and text; ValueError and generic exceptions return bare error strings. LLM cannot determine if it should retry, ask user, or abandon the operation.
Parameter descriptions lack format/example guidance. 'q' description says 'Basic search query string' but does not explain what a valid query looks like, whether wildcards are supported, or length limits. 'search_type' examples are present but descriptions are minimal.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 48 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 41 | - | v1 |
Tool description does not state what the tool does or when to use it clearly. It lists features but does not explain: 'Use this to find music by artist name, track title, album, or other Spotify content types. Returns matching results with metadata.'
No result limiting documented. Spotify search can return hundreds of results; tool does not specify a max result count or pagination support in the description, risking context window exhaustion.