Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search

Read-onlyIdempotent

Search Spotify's catalog for tracks, artists, albums, playlists, shows, episodes, or audiobooks. 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. Changed3 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / offset / default
      Added value: +0
  2. 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}$"
  3. 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"
+]
  4. First observedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds non-obvious behavior beyond those annotations: passing types suppresses track/album fallback noise, and results are capped at 10 per type. It does not contradict the annotations.

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, front-loaded with the primary purpose, then immediately useful guidance on types and sibling-tool selection. No filler, no repetition of schema fields, and every sentence earns its place.

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?

Given the read-only annotations, fully documented 8-parameter schema, and the response_format parameter, the description covers the key contextual needs: what it searches, how to narrow results, and which sibling tools to use for deeper or newer searches. It is not exhaustive about output layout, but the schema and response_format enum already carry that burden.

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 coverage is 100%, so the baseline is 3, and the description does not need to restate parameter definitions. It adds value by clarifying that the types array produces a single-kind search with no fallback noise and by tying the limit to the ≤10/type behavior. Other parameters are already well documented in the schema.

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 specific verb and resource ('Search Spotify's catalog') and enumerates the seven content types searched. It also distinguishes the tool from sibling search tools by naming them in the decision guide, so an agent can separate it from search_deep, search_fresh, and search_by_isrc.

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 lists when to use this tool (general, ≤10/type) versus search_deep, search_fresh, search_by_isrc, and whats_new. It also explains the types-array behavior for single-kind searches. This is clear, actionable routing guidance rather than vague context.

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