Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

start_podcast_session

Launch a planned podcast listening session on a Spotify device, queueing episodes and starting the first at its resume point; use preview mode to validate without playback.

Instructions

Plan a podcast session (see plan_podcast_session) and start it on a device. Limitation: Spotify cannot apply resume offsets when queueing — only the first episode can start at its resume point (via PUT /me/player/play on its show context); later episodes are appended to the queue and play from the beginning. With dry_run, nothing is played or queued.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoRestrict the source: 'episodes' = your saved episodes only, 'shows' = recent episodes of your saved shows only. Omit to use saved episodes (plus saved shows when saved_only is false)
marketNoISO 3166-1 alpha-2 country code for the saved-show episode lookups, e.g. "US". Defaults to SPOTIFY_MCP_MARKET, then to the account country — these lookups are market-gated, so a wrong default silently drops episode rows. Ignored for a saved-episodes-only plan.
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
minutesYesSession length in minutes (1–480)
device_idNoTarget device ID; omit for the active device
saved_onlyNoWhen no kind is set, include recent episodes of saved shows too. Default: true (saved episodes only)
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
    • addedInput schema / properties / market
      Added value: +{
+  "description": "ISO 3166-1 alpha-2 country code for the saved-show episode lookups, e.g. \"US\". Defaults to SPOTIFY_MCP_MARKET, then to the account country — these lookups are market-gated, so a wrong default silently drops episode rows. Ignored for a saved-episodes-only plan.",
+  "pattern": "^[A-Za-z]{2}$",
+  "type": "string"
+}
  2. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.26.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations supply only destructiveHint=false, so the description carries most of the behavioral burden and does so well: it discloses a real, non-obvious constraint about Spotify resume offsets when queueing and clarifies that dry_run plays/queues nothing. It doesn't state whether starting a session interrupts current playback or whether a device must be active, which are relevant mutation side effects.

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

Conciseness4/5

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

Three sentences, front-loaded with the purpose, then the limitation, then the dry_run caveat. The limitation sentence is dense but each clause carries information an agent needs; nothing is padded.

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 an 8-parameter playback tool with full schema coverage and no output schema, the description covers purpose, sibling routing, a key platform limitation, and dry_run behavior. It omits what a session result looks like and any playback-interruption or device-state side effects, which are the remaining gaps.

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%, so the baseline is 3. The description's note that 'with dry_run, nothing is played or queued' restates the schema's dry_run description rather than adding new semantics, and no other parameter is elaborated.

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+resource ('Plan a podcast session ... and start it on a device') and explicitly distinguishes itself from the sibling plan_podcast_session by the fact that it starts playback. An agent can tell the two apart without opening either schema.

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?

It routes the agent to plan_podcast_session for planning-only and explains the dry_run mode as the no-playback path, giving clear context for when each behavior applies. It stops short of naming exclusions versus general playback tools like play or add_to_queue.

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