Skip to main content
Glama
llyfn

Spotify MCP Server

by llyfn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_followed_artists

Retrieve the current user's followed artists from Spotify with cursor-based pagination. Use the after cursor to fetch additional pages and limit results as needed.

Instructions

Get the current user's followed artists. Cursor-paginated.

    To follow or unfollow, use `save_to_library` / `remove_from_library` with Spotify URIs.

    Args:
        limit: Maximum number of artists to return (1-50, default 20).
        after: Cursor (last artist ID from previous page) to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses cursor-pagination and the semantics of the 'after' cursor, but omits auth/scope requirements, rate-limit behavior, and whether results are cached or scoped to the current user only.

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?

Front-loads the purpose in the first sentence, follows with pagination and alternative-tool guidance, then parameter details. The 'Args:' block is slightly redundant in format but every line carries real information.

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?

For a two-parameter read tool with an output schema (so return values need not be explained) and full parameter documentation, the description is essentially complete. Only auth/scope context is missing, a minor gap.

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 compensate, and it does: it documents both parameters fully, including the limit range (1-50) and default (20) plus the cursor's meaning (last artist ID from previous page). This is meaning beyond the bare schema types.

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?

States a specific verb+resource ('Get the current user's followed artists'), which distinguishes it from sibling list tools like get_saved_albums and get_saved_tracks. It doesn't explicitly name a sibling it competes with, but the resource is 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?

Provides clear routing guidance by naming the alternative tools (save_to_library / remove_from_library) for the follow/unfollow case, telling the agent when NOT to use this tool. It doesn't cover other conditions like empty-library edge cases, but the primary disambiguation is present.

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