Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_followed_artists

Retrieve all artists a Spotify user follows with cursor-based pagination. Use it to audit, analyze, or visualize followed artists, with configurable page size and result limits.

Instructions

Get all artists the user follows (cursor-based pagination)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoArtist ID cursor for pagination (from previous response)
limitNo1–50. Default: 20
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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 / 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"
+}
  2. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations carry no burden here (none provided), so the description must disclose behavior itself. 'Cursor-based pagination' is a genuine, non-obvious behavioral disclosure that tells the agent results arrive in pages tied to an artist-ID cursor. However, it does not state the read-only nature, auth reliance, response shape, or how limit/max_results interact; the one disclosed trait earns a 3 but nothing more.

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?

A single front-loaded sentence with zero filler: verb, resource, and the key pagination behavior are all present and ordered usefully. Every word earns its place.

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

Completeness3/5

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

For a relatively simple list tool, the schema covers all parameter semantics and the description names the operation and pagination mode. But with no annotations and no output schema, the agent gets no information about the return structure, cursor continuation mechanics beyond a hint, or how response_format alters the payload — adequate for invocation, yet with clear gaps.

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% — all four parameters (after, limit, max_results, response_format) are fully documented with ranges, defaults, and meanings. The description only reinforces the cursor concept already present in the schema's 'after' parameter, so it stays at the baseline 3 without adding extra semantic value.

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?

The description uses a specific verb and resource — 'Get all artists the user follows' — and scopes it with 'all' and 'the user follows', which distinguishes it from siblings like get_artist (single artist) and check_following_artists (specific artist checks). The cursor-based pagination note adds further precision about the operation's scope.

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?

No when-to-use or when-not-to-use guidance is provided, and no alternative tools are named. With closely related siblings such as check_following_artists, following_analytics, and export_followed_artists present, an agent must infer selection criteria entirely from the tool name and schema. The pagination hint is mechanical, not usage guidance.

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