Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_show_episodes

Retrieve episodes of a podcast show by Spotify ID, supporting pagination, market filtering, and fetching all results.

Instructions

[Deprecated] use list_show_episodes — List a podcast show's episodes with pagination. Alias kept for backward compat; forwards to same GET /shows/{id}/episodes as list_show_episodes. Resume positions require the user-read-playback-position scope. Also covers: show episode listing, paged podcast episodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSpotify show ID
limitNoResults per page, 1–50. Default: 20
marketNoISO 3166-1 alpha-2 country code. If given, only shows and episodes available in that market are returned.
offsetNoIndex of the first episode to return. Default: 0
fetch_allNoWhen true, walk all pages via getAllPages up to cap (fetch_all_cap) — use for "all" queries. Default: false
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 changedv1.28.0
    • addedInput schema / properties / fetch_all
      Added value: +{
+  "description": "When true, walk all pages via getAllPages up to cap (fetch_all_cap) — use for \"all\" queries. Default: false",
+  "type": "boolean"
+}
  2. Changed5 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / market / pattern
      Added value: +"^[A-Za-z]{2}$"
    • 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 / maximum
      Added value: +9007199254740991
    • 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"
+}
  3. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses the deprecation, the forwarding behavior, the HTTP GET endpoint, pagination, and the user-read-playback-position scope requirement. It does not mention output format or rate limits, but for a read-only alias the key behaviors are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The important information is front-loaded: deprecation, replacement, alias, and endpoint. However, the final sentence 'Also covers: show episode listing, paged podcast episodes' is redundant filler that restates the purpose without adding value.

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 7 parameters are fully documented in the schema and there is no output schema, the description provides the essential context: deprecation, canonical sibling, shared endpoint, and auth scope. An agent knows to route to list_show_episodes. Return-shape details are unnecessary for a deprecated alias.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The tool description adds little beyond referring to pagination and the auth scope; it does not clarify parameter usage beyond what the schema already provides.

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: 'List a podcast show's episodes with pagination.' It also marks the tool as deprecated and explicitly names list_show_episodes as the intended alternative, making its role as a backward-compat alias unmistakable.

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 description explicitly says 'use list_show_episodes' and clarifies that this tool is an alias kept only for backward compatibility, forwarding to the same endpoint. This gives an agent clear, actionable routing guidance: avoid this tool and use the named sibling.

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