Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search

Find tracks, artists, albums, playlists, shows, episodes, or audiobooks in Spotify's catalog. Specify content types to get precise results without fallback noise.

Instructions

Search Spotify's catalog for tracks, artists, albums, playlists, shows, episodes, or audiobooks. Pass types as an array (e.g. ["artist"]) to search a single kind — no track/album fallback noise. Decision guide: search (general, ≤10/type), search_deep (paginated fetch_all up to 50/type), search_fresh (tag:new last 2 weeks), search_by_isrc (exact ISRC), whats_new (personal radar from follows).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per type, 1–10. Default: 5
queryYesSearch query
typesNoContent types to search, as an array. Default: ["track","artist","album"]. Pass e.g. ["artist"] for an artist-only search. "audiobook" is only available in the US, UK, CA, IE, NZ and AU markets.
marketNoISO 3166-1 alpha-2 country code, e.g. 'US' — uppercased automatically
offsetNoIndex of the first result to return, 0–1000. Use with limit to page through results
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
include_externalNoPass "audio" to include externally-hosted audio items marked as playable

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.28.0
    • changedInput schema / properties / market / description
      Previous value: -"ISO 3166-1 alpha-2 country code"New value: +"ISO 3166-1 alpha-2 country code, e.g. 'US' — uppercased automatically"
    • addedInput schema / properties / market / pattern
      Added value: +"^[A-Za-z]{2}$"
  2. Changed7 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / include_external
      Added value: +{
+  "description": "Pass \"audio\" to include externally-hosted audio items marked as playable",
+  "enum": [
+    "audio"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Max items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)",
+  "exclusiveMinimum": 0,
+  "maximum": 2000,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Index of the first result to return, 0–1000. Use with limit to page through results",
+  "maximum": 1000,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / types / description
      Previous value: -"Content types to search, as an array. Default: [\"track\",\"artist\",\"album\"]. Pass e.g. [\"artist\"] for an artist-only search."New value: +"Content types to search, as an array. Default: [\"track\",\"artist\",\"album\"]. Pass e.g. [\"artist\"] for an artist-only search. \"audiobook\" is only available in the US, UK, CA, IE, NZ and AU markets."
    • changedInput schema / properties / types / items / enum
      Previous value: -[
-  "track",
-  "artist",
-  "album",
-  "playlist",
-  "show",
-  "episode"
-]New value: +[
+  "track",
+  "artist",
+  "album",
+  "playlist",
+  "show",
+  "episode",
+  "audiobook"
+]
  3. First observedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses a non-obvious behavior: single-type searches produce no track/album fallback noise, and it clarifies per-type result limits. While it doesn't discuss result shape or rate limits, a read-only catalog search has minimal side-effect risk, and the stated behaviors are meaningful and beyond schema info.

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 sentences with no wasted words: purpose, usage nuance, and sibling routing. The most decision-relevant information is front-loaded, and the decision guide is compactly formatted for scannability.

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 an 8-parameter tool with no output schema and no annotations, this is nearly complete. The schema covers all parameter details, and the description supplies the missing cross-tool routing and types-array nuance. Minor omissions like explicit return-value shape and market restrictions for audiobooks are either already in the schema or low-risk for a search tool.

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 description coverage is 100%, so the baseline is 3. The description adds value by giving a concrete example for `types`, explaining the behavioral consequence of using a singleton array, and tying the tool's result limits to the decision guide. This goes beyond the schema's plain property descriptions.

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 states a precise verb ('Search Spotify's catalog') and enumerates every supported item type, making the tool's scope unambiguous. It also distinguishes itself from sibling search tools in the decision guide, so an agent can tell them apart without inspecting schemas.

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

Usage Guidelines5/5

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

The decision guide explicitly maps conditions to alternatives: general ≤10/type for this tool, paginated fetch_all for search_deep, tag:new for search_fresh, exact ISRC for search_by_isrc, and personal radar for whats_new. It also instructs agents to pass a singleton types array to avoid fallback noise, which is a clear when/how-to-use directive.

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