Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

search

Query Spotify's catalog for tracks, albums, artists, playlists, shows, episodes, or audiobooks using filters like artist, album, year, genre, ISRC, and UPC.

Instructions

Search for tracks, albums, artists, playlists, shows, episodes, or audiobooks on Spotify.

    Args:
        query: Search query. Supports filters: artist:, album:, track:, year:, genre:,
            isrc: (track ISRC), upc: (album UPC). Use NOT/OR with quotes for refinement.
        types: Comma-separated types: track, album, artist, playlist, show, episode, audiobook.
        limit: Maximum results per type (1-10, default 10).
        offset: Index of first result to return (default 0).
        market: ISO 3166-1 alpha-2 country code to filter results.

Input Schema

Name	Required	Default
`limit`	No
`query`	Yes
`types`	No	track
`market`	No
`offset`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful constraints beyond the schema — the limit range (1-10) and default, the filter syntax for query, and the expected market format — but says nothing about rate limits, authentication, or result caps per type.

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?

Front-loads the one-line purpose, then a compact Args block, one line per parameter. No filler; every sentence carries information an agent needs.

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?

An output schema exists so return values need not be described, and all five parameters are documented. It is nearly complete for a catalog search; only auth/rate-limit context is missing, which is minor given the fully documented parameter surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: every one of the five parameters is explained with meaning beyond the schema. The query filter operators (artist:, album:, track:, year:, genre:, isrc:, upc:, NOT/OR) and the limit range/default are especially valuable additions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Search") and enumerates the searchable resources (tracks, albums, artists, playlists, shows, episodes, audiobooks), which is clearly distinct from the get_* siblings. It stops short of explicitly naming a sibling alternative, but the scope is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance and no routing to alternatives such as get_track or get_album for direct lookups. Usage is only implied by the resource enumeration; an agent gets no guidance on choosing search over the many lookup siblings.

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