Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_album_tracks

Retrieve an album's track list with pagination, market filtering, and optional fetch-all for complete results.

Instructions

List the tracks of an album with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSpotify album ID
limitNoResults per page, 1–50. Default: 20
marketNoISO 3166-1 alpha-2 country code. Defaults to the account country; affects track availability.
offsetNoIndex of the first track 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
      Added value: +{
+  "description": "ISO 3166-1 alpha-2 country code. Defaults to the account country; affects track availability.",
+  "pattern": "^[A-Za-z]{2}$",
+  "type": "string"
+}
    • 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

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'list' and 'pagination', leaving out pagination semantics, result shape, market behavior, and potential large-response considerations. This is a minimal disclosure for an unannotated tool.

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?

The description is a single, front-loaded sentence with no filler or redundant restatement of the tool name. It is appropriately short, though it lacks extra context that would make it more informative.

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?

For a straightforward read-only list tool, the schema covers parameter details well. However, the absence of usage guidance, behavioral context, and output-shape information leaves noticeable gaps for an agent deciding how to format results and when to prefer this tool over siblings.

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%, with all seven parameters already documented including defaults and bounds. The description only adds the generic notion of pagination, which does not meaningfully extend what the schema already says. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 the tracks of an album'. It also mentions pagination, which is the core operation. However, it does not explicitly distinguish this from related siblings like get_album, which may also return track lists, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives such as get_album or get_playlist_items. No exclusions or preference conditions are mentioned, so an agent must infer usage solely from the name.

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