Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Artist

get_artist

Read-onlyIdempotent

Retrieve details for one or more Spotify artists in a single request. Returns artist information in the requested order, plus top tracks when requesting one artist.

Instructions

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

Args:
    artist_ids: One artist ID/URI, or a list of up to 50. A list costs one
        Spotify request rather than one per artist.
Returns:
    ArtistInfo whose `artists` follows the order requested. `top_tracks` is
    filled only when a single artist was requested, and is empty rather than
    an error when Spotify withholds that endpoint.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`artist_ids`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`artists`	Yes
`top_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?

Goes beyond the readOnly/idempotent/openWorld annotations by disclosing concrete behavior: results preserve request order, top_tracks is populated only for single-artist requests, and withheld endpoints yield an empty list instead of an error. This is exactly the kind of edge-case behavior an agent needs to interpret responses correctly.

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 compact and well-structured, with Args and Returns sections that each add necessary detail. There is no filler or repetition; every sentence contributes a distinct fact about invocation or response behavior.

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?

For a single-parameter read-only tool with an output schema and safety annotations, the description covers invocation, batching, ordering, and edge-case return behavior. Nothing an agent needs to call it correctly or interpret its result is missing.

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 provides only the property name and type, but the description fully explains the parameter's meaning: an artist ID/URI, a list of up to 50, and the request-count implication. With one parameter and 0% schema coverage, the description carries the entire semantic burden and succeeds.

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?

States a specific verb ('Get details') and a specific resource ('Spotify artists'), and clarifies that the call supports batching one or more up to 50 artists. This distinguishes it from sibling tools like get_tracks, get_album, or get_playlist without requiring schema inspection.

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?

Provides clear usage context: it can accept a single ID/URI or a list, with an explicit batching note that a list costs one Spotify request rather than one per artist. It doesn't name alternatives or list exclusions, but the resource scope is clear enough that an agent can decide when to call this tool.

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