Spotify MCP has well-structured schemas for most tools, but suffers from critical gaps in parameter descriptions and output documentation. 7 of 9 tools lack parameter descriptions entirely (e.g., search tool has empty input schema with no guidance). Tool descriptions are present but generic (avg 45 chars, well below 194-char baseline). No output schemas documented. Error handling is absent, no recovery guidance or actionable error messages. Naming is verb-first and clear (get_, create_, add_, search_), which is good. However, the lack of parameter documentation and missing output schemas severely limit LLM reasoning and tool composition.

• Add parameter descriptions to search tool: 'query' (string, required, e.g. 'artist:Taylor Swift track:Lover'), 'type' (enum: track|artist|album|playlist), 'limit' (integer, 1-50, default 20). Document output schema with fields: results[], each containing id, name, type, uri.
• Document output schemas for all tools. Example for get_user_playlists: {playlists: [{id, name, description, public, owner, total_tracks}], total: number, limit: number, offset: number}. This enables LLM to chain calls (e.g., get_user_playlists → add_to_playlist using returned id).
• Expand parameter descriptions with format and constraint hints. For add_to_playlist trackUris, add: 'Array of Spotify track URIs (format: spotify:track:TRACK_ID). Example: ["spotify:track:3n3Ppam7vgaVa1iaRUc9Lp"]'. For play_pause action, clarify: 'Set to "play" to start playback or "pause" to stop. Does not toggle, must specify desired state.'
• Add error handling with recovery guidance. Wrap API calls in try-catch; return structured errors like {error: 'Playlist not found', code: 'PLAYLIST_NOT_FOUND', suggestion: 'Call get_user_playlists() to find valid playlist IDs'}. This guides LLM to self-correct.
• Add pagination constraints to get_user_playlists: limit (integer, 1-50, default 20), offset (integer, ≥0, default 0). Return total_count in response so LLM knows when to stop paginating. Document in description: 'Returns up to 20 playlists per call. Use offset to fetch additional pages.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry