Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_artist_albums

Fetches an artist's albums and singles from Spotify using their artist ID, with options to filter by album type and paginate results.

Instructions

List an artist's albums and singles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSpotify artist ID
limitNoResults per page, 1–10. Default: 10
marketNoISO 3166-1 alpha-2 country code. Defaults to the account country; affects album availability.
offsetNoIndex of the first album 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)
include_groupsNoAlbum types to include. Default: ["album","single"]
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. Changed7 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page, 1–50. Default: 20"New value: +"Results per page, 1–10. Default: 10"
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +10
    • addedInput schema / properties / market
      Added value: +{
+  "description": "ISO 3166-1 alpha-2 country code. Defaults to the account country; affects album 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
      Added value: +{
+  "description": "Index of the first album to return. Default: 0",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "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"
+}
  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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List', and says nothing about pagination, fetch_all behavior, response format, max_results limits, market-dependent availability, or whether multiple album groups are combined by default.

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 repetition. It is appropriately brief, though it is so terse that it omits useful context that a structured description could have added.

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

Completeness2/5

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

With 8 parameters, no output schema, no annotations, and many closely related sibling tools, the description is underspecified. An agent gets no sense of return shape, pagination behavior, or how this tool differs from overlapping siblings, so the tool-level context is incomplete.

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 8 parameters already have meaningful documentation. The description adds only the 'albums and singles' scope, which aligns with the include_groups default, but it does not compensate for or explain the pagination and formatting parameters beyond what the schema provides.

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 concrete action ('List') and a specific resource scope ('an artist's albums and singles'), so an agent can tell what the tool does. It does not explicitly differentiate itself from sibling tools like get_artist_singles or get_artist_discography, so it falls just 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 one-sentence description gives no guidance on when to use this tool over get_artist_singles, get_artist_discography, or get_artist_appearances. There are no exclusions, conditions, or suggested alternatives, leaving the agent to infer selection purely 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