Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_saved_shows

Read-onlyIdempotent

Search saved podcast shows by name or publisher, using a bounded scan and local filtering to find matches in your Spotify library.

Instructions

Search saved podcast shows (bounded walk + client-side filter). Quota: GET /me/shows paged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSubstring match against show name and publisher. Spotify removed `publisher` from show payloads in February 2026, so the publisher half can only match on an app registration created before November 2024; on a current registration this is a name search that reports 0 publisher matches rather than pretending to have searched publishers.
scan_capNoMaximum saved items to scan; defaults to SPOTIFY_MCP_FETCH_ALL_CAP
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • changedInput schema / properties / query / description
      Previous value: -"Substring match against show name/publisher"New value: +"Substring match against show name and publisher. Spotify removed `publisher` from show payloads in February 2026, so the publisher half can only match on an app registration created before November 2024; on a current registration this is a name search that reports 0 publisher matches rather than pretending to have searched publishers."
  2. 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 / scan_cap / description
      Added value: +"Maximum saved items to scan; defaults to SPOTIFY_MCP_FETCH_ALL_CAP"
  3. Addedv1.26.1

TDQS

A4/5.0
Behavior4/5

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

Annotations cover readOnly and idempotent, and the description adds behavior beyond them: the search is a bounded walk with client-side filtering (implies pagination/scan cost) and it is subject to a paged GET /me/shows quota. It does not state the scan default or what happens when scan_cap is exceeded, but the mechanism disclosure is genuinely useful.

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 tightly packed sentences with zero filler; the what and the how are front-loaded, and the quota caveat follows. Nothing is redundant with the schema or annotations.

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 a read-only search tool with no output schema, the definition supplies purpose, mechanism, and quota context. It leaves the scan/return-volume semantics and any ordering of results implicit, but the essentials for correct invocation are present.

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 the schema's query parameter description is notably rich (substring match target, publisher-removal caveat). The description adds no parameter-level detail of its own, so the baseline 3 applies since the schema carries the load.

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 and resource ('Search saved podcast shows') with a scoping distinction that separates it from get_saved_shows (unfiltered listing) and from search_saved_episodes/albums/audiobooks (different media type). The parenthetical '(bounded walk + client-side filter)' further pins down what kind of search this is.

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?

The phrase 'client-side filter' implies the tool walks saved items locally rather than querying server-side, and the quota note ('GET /me/shows paged') hints at call cost, which indirectly signals when to prefer cheaper alternatives. However, no explicit when-to-use or when-not-to-use guidance or named alternative is given.

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