Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Album

get_album

Read-onlyIdempotent

Retrieve details for one or more Spotify albums in a single request. Supports up to 20 album IDs or URIs, returning album info in requested order, with track lists included for single-album queries.

Instructions

Get details for one or more Spotify albums, batched into a single request.

Args:
    album_ids: One album ID/URI, or a list of up to 20 — Spotify's own cap
        for album batches, which is lower than the 50 for tracks and artists.

Returns:
    AlbumInfo whose `albums` follows the order requested. `tracks` holds the
    album's track list only when a single album was requested.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`album_ids`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`albums`	Yes
`tracks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.6.1Sep 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds valuable behavioral context: the exact batch limit of 20, the request order preservation in the response, and the conditional inclusion of tracks only for single-album requests. This goes beyond the annotations to explain how the tool behaves in edge cases.

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 well-structured: a one-sentence purpose, then a clear Args section, then Returns. Every sentence adds value—no filler. The batching cap and response behavior are front-loaded, and the format is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the simple schema (one parameter), the tool has nuanced behavior around batching and response shape. The description covers both the parameter format and the return semantics (order preservation, conditional tracks). With an output schema present, the description does not need to repeat everything, but it explains the key non-obvious aspects completely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero description coverage, but the description fully compensates: it explains that album_ids can be a single ID/URI or a list up to 20, and even clarifies Spotify's cap. This is essential information an agent needs to invoke the tool correctly, and it is not available from 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 clearly states 'Get details for one or more Spotify albums, batched into a single request', identifying the specific verb, resource, and batching behavior. It distinguishes itself from sibling tools like get_tracks and get_artist by focusing on albums and noting the batch cap difference (20 for albums vs 50 for tracks/artists), making it unambiguous.

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?

The description implies usage context by explaining batching and the batch cap, and clarifies that tracks are only returned for single-album requests. However, it does not explicitly say when not to use this tool or point to alternatives (e.g., 'for track details use get_tracks'). The batching context is clear but the exclusions are absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.