Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_saved_shows

Read-onlyIdempotent

Retrieve podcast shows saved in your Spotify library. Use fetch_all to get the complete collection, with pagination controls for partial results.

Instructions

Get podcast shows saved in the user's library. Set fetch_all=true to retrieve the entire collection. Output is capped by max_results (default: SPOTIFY_MCP_MAX_ITEMS).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1–50. Default: 20
offsetNoPagination offset. Default: 0
fetch_allNoFetch all pages instead of one page (ignores limit/offset)
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.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed5 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / fetch_all / description
      Previous value: -"Fetch all pages instead of one page (ignores limit/offset; capped at 500 items)"New value: +"Fetch all pages instead of one page (ignores limit/offset)"
    • 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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavioral context by mentioning that output is capped by max_results and that fetch_all retrieves the entire collection, which goes beyond the annotations without contradicting them.

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 sentences with no extraneous information. The purpose is stated first, followed by the most relevant options (fetch_all and max_results). Every word earns its place.

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 list tool with 5 parameters fully documented in the schema and safety covered by annotations, the description is sufficient. It explains the core behavior and key options, though it does not describe return format or pagination details, which are partially covered by the schema.

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 coverage is 100%, so all parameters are documented. The description reiterates fetch_all and max_results behavior but adds little beyond what the schema descriptions already provide. The baseline of 3 is appropriate given the schema carries the parameter documentation.

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 clearly states the tool retrieves podcast shows saved in the user's library, specifying a distinct resource ('saved shows') that separates it from siblings like get_show_details or list_show_episodes. The verb 'Get' and the resource are explicit and unambiguous.

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 description implies usage for fetching saved shows but does not explicitly differentiate from list_saved_shows or other show-related tools. It offers internal guidance on fetch_all and max_results but no when-to-use vs alternatives, relying on the name to convey 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