Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

Check Followed Artists

check_following_artists

Read-onlyIdempotent

Check if you follow specific artists on Spotify by providing their IDs or URIs, returning a true/false status for each artist, up to 50 per request.

Instructions

Check which artists the user follows. One request for up to 50.

Artists are followed rather than saved, so this reads follows, not the
saved-albums library.

Args:
    artist_ids: Artist IDs or URIs (up to 50)
Returns:
    MembershipStatus.results maps each Spotify artist id to true if followed

Input Schema

TableJSON Schema

Name	Required	Description	Default
`artist_ids`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`checked`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.6.1Sep 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, and idempotent hints. The description adds beyond them: it clarifies the follow-state source, batching limit of 50, and the return mapping from artist id to boolean. No contradiction exists.

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?

Four compact sentences plus Args/Returns block with no filler. The core purpose is front-loaded, and every sentence earns its place.

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 rich annotations and an output schema, the description fully covers input semantics, batch limit, and conceptual distinction. Nothing essential is missing.

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 coverage is 0%, so the description must compensate, and it does: artist_ids accepts Artist IDs or URIs up to 50 and the result maps each Spotify artist id to true if followed. It could add exact URI format, but this is adequate.

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 and resource: 'Check which artists the user follows.' It immediately distinguishes follows from saved albums, so it is clearly differentiated from check_saved_albums and other sibling tools.

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 context by explaining that artists are followed rather than saved, so the tool reads follows, not the saved-albums library. It does not name a sibling explicitly, but the exclusion is explicit enough for an agent to route correctly.

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