Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_saved_tracks

Read-onlyIdempotent

Retrieve tracks from your Liked Songs. Use fetch_all to get the entire collection, or paginate with limit and offset for specific pages.

Instructions

Get tracks saved in the user's Liked Songs. 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
marketNoISO 3166-1 alpha-2 country code, e.g. 'US'
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. Changed4 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 / fetch_all / default
      Added value: +false
    • addedInput schema / properties / offset / default
      Added value: +0
  2. 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}$"
  3. 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"
+}
  4. First observedv1.0.1

TDQS

A4.2/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 meaningful behavioral details not in annotations: fetch_all toggles full-collection retrieval, and max_results caps output with an environment-driven default. This is exactly the kind of context that helps an agent predict cost and scope.

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?

Three tight sentences: the purpose comes first, followed by the two behavioral knobs that matter. No filler, no repetition of schema content. Efficient and front-loaded.

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 collection fetch with no output schema, the description covers the main behavioral questions: what it returns, how to get everything, and how results are capped. The remaining params (limit, offset, market, response_format) are fully documented in the schema, and response_format's enum explains the return shape. Complete enough given the tool's simplicity.

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 descriptions cover 100% of the 6 parameters with types, defaults, ranges, and enums, so the description doesn't need to re-document them. The description does reinforce the two decision-relevant params (fetch_all, max_results) in plain language, adding a small amount beyond schema. Baseline 3 is appropriate.

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, resource, and collection semantics: retrieves tracks saved in the user's Liked Songs. This distinguishes it from siblings like get_saved_albums, get_saved_episodes, and search_saved_tracks. Also surfaces the key options fetch_all and max_results, making the tool's scope immediately clear.

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?

Gives clear operational context: how to request the full collection (fetch_all=true) and how output is bounded (max_results, defaulting to SPOTIFY_MCP_MAX_ITEMS). It does not explicitly name alternatives or exclusions, but the read-only, single-collection scope is unambiguous. No misleading guidance.

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