Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_album

Retrieve album details and track list using a Spotify album ID.

Instructions

Get album details and track list by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSpotify album ID
marketNoISO 3166-1 alpha-2 country code. Defaults to the account country; affects track playability.
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.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 playability.",
+  "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 / 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"
+}
  2. First observedv1.0.1

TDQS

B3.3/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 does not state that this is a read-only fetch, describe the output structure, mention market-dependent playability, or note pagination/max_results behavior. These are meaningful gaps for a tool with no annotation safety net.

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?

The description is a single, front-loaded sentence with no filler or redundancy. It efficiently communicates the core action and scope.

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?

The description is sufficient to understand the basic invocation (fetch single album by ID), especially with a fully described schema. However, with no output schema and no usage differentiation from get_album_tracks or get_several_albums, the definition leaves gaps around output shape and tool selection.

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 all four parameters are already well-documented in the schema. The description's 'by ID' aligns with the required id property and 'track list' loosely relates to max_results/response_format, but it adds no new semantic value beyond the schema.

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 ('Get'), a resource ('album details and track list'), and a clear key qualifier ('by ID'). This immediately distinguishes it from siblings like get_several_albums (multiple IDs) and get_album_tracks (tracks only).

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?

There is no explicit guidance on when to use this tool vs. alternatives such as get_album_tracks, get_several_albums, or get_artist_albums. The only usage signal is the 'by ID' qualifier, which is too weak to help an agent select correctly among similar album-related tools.

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