Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

show_episode_search

Find episodes in a specific show by searching episode titles and descriptions for a keyword or phrase.

Instructions

Full-text search within one show's episodes (GET /shows/{id}/episodes paged + client-side q). Quota: 🟡 1–N pages (fetch_all walks).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per page for the underlying paging, 1–50. Default: 20
queryYesCase-insensitive substring over name/description
marketNoISO 3166-1 alpha-2 country code, e.g. 'US'
offsetNoOffset for underlying paging. Default: 0
show_idYesSpotify show ID
fetch_allNoWhen true, walk all pages (up to cap) to find matches
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. 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

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that this is a paged GET with client-side filtering and that fetch_all can walk multiple pages, along with a quota indicator. This is genuine behavioral context beyond the name and schema.

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 short sentences with no filler; the core scope and endpoint are front-loaded, and the quota warning is placed second. Every phrase earns its place.

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 description explains the implementation and quota, and the schema fully documents parameters, but there is no output schema and no annotation safety/behavior context. It could be more complete about return behavior or explicit routing to global search tools, so it is adequate but not fully self-sufficient.

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. The description adds value by revealing that the query is applied client-side after paging and that fetch_all drives page-walking, which materially affects how limit, offset, query, and quota interact.

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 names a specific verb ('search') and a specific resource ('one show's episodes'), and states the exact endpoint. The scoping phrase 'within one show's episodes' cleanly separates it from global search_episodes and from listing tools like get_show_episodes.

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

Usage Guidelines4/5

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

The scope is clear: use this when you need full-text search inside a single show rather than across all shows or just listing episodes. It does not explicitly name the sibling alternatives or give when-not-to-use conditions, but the one-show constraint provides unambiguous 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