Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

get_artist_albums

Retrieve albums by a Spotify artist using an artist ID, optionally filtering by album type, market, and pagination to browse releases.

Instructions

Get albums by a Spotify artist.

    Args:
        artist_id: The Spotify ID of the artist.
        include_groups: Comma-separated album types: album, single, appears_on, compilation.
        limit: Maximum number of albums to return (1-10, default 10).
        offset: Index of the first album to return (default 0).
        market: ISO 3166-1 alpha-2 country code.

Input Schema

Name	Required	Description	Default
`limit`	No
`market`	No
`offset`	No
`artist_id`	Yes
`include_groups`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Sep 29, 2026
- changedInput schema / properties / limit / default
```
Previous value: -20New value: +10
```

Changed1 schema field changedv0.2.0Jun 9, 2026

addedInput schema / properties / market

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Market"
+}

First observedv0.1.1May 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose pagination behavior (limit 1-10 with default 10, offset default 0) and the accepted include_groups values, but says nothing about authentication requirements, rate limits, or what appears_on results imply. It adds useful operational context but leaves notable behavioral gaps for a read tool with zero annotation coverage.

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 purpose sentence is front-loaded and each Arg line earns its place. The Google-docstring formatting is slightly heavier than prose but contains no filler.

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?

With an output schema present, return-value documentation is unnecessary, and the description covers purpose, all five parameters, and pagination defaults. The main omission is guidance on how market and include_groups interact with results, which would help an agent call it correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must supply all parameter meaning, and it does: artist_id as the Spotify ID, include_groups enumerating album/single/appears_on/compilation, limit with range and default, offset as a start index, and market as an ISO 3166-1 alpha-2 code. Only the required/optional distinction is left implicit.

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 opening sentence states a specific verb (Get) and resource (albums) scoped to a Spotify artist, which is clearly distinct from siblings like get_album (single album) and get_artist (artist metadata). It does not explicitly name those siblings, so differentiation is implicit rather than stated.

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 guidance on when to choose this tool over get_album, get_album_tracks, or get_artist. The Args block implies the kinds of filtering available, but nothing tells the agent which situations call for this endpoint or any prerequisites.

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