Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_playlists

Search Spotify playlists using a query string, with adjustable result limit, market, and offset. Returns results in concise, detailed, or JSON format.

Instructions

Search playlists only (GET /search?type=playlist). Quota: 🟢 single.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per type, 1–10. Default: 5
queryYesSearch query
marketNoISO 3166-1 alpha-2 country code, e.g. 'US'
offsetNoIndex of the first result to return, 0–1000
max_resultsNoMax items to return
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
include_externalNoPass "audio" to include externally-hosted audio items

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'"
    • addedInput schema / properties / market / pattern
      Added value: +"^[A-Za-z]{2}$"
  2. Addedv1.26.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are present, so the description carries the burden. It usefully discloses quota ('🟢 single') and the GET endpoint, which implies a read-only, low-cost operation, but it does not explicitly state safety, pagination behavior, or what happens on errors.

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?

Two compact sentences with the core scope front-loaded. The quota note is minimal and informative; there is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The input schema is rich, but with no output schema and no annotations, the description leaves the agent to infer return shape and how this tool relates to generic search or other search variants. It is adequate for making a simple call but not fully complete.

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

Parameters3/5

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

Schema description coverage is 100% and every parameter already has a description. The tool description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb ('Search') and resource ('playlists'), and scopes it with 'only' plus the endpoint (GET /search?type=playlist). This clearly differentiates it from the generic 'search' and the many sibling search_tracks/search_artists/search_albums tools.

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

Usage Guidelines3/5

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

'Search playlists only' implies when the tool should be used, but it does not name alternatives such as 'search' for multi-type results or explicitly say when not to use this tool. The usage context is inferable rather than stated.

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