Skip to main content
Glama
Sign In
Spotify MCP Server

Spotify MCP Server

by walter-kai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

spotify_follow_artists

Follow one or more Spotify artists by submitting their artist IDs, keeping their music in your followed artists list.

Instructions

Follow one or more artists

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "artist_ids": "<artist_ids>"
    },
    "name": "spotify_follow_artists"
  }
}

Input Schema

NameRequiredDescriptionDefault
artist_idsYesArray of Spotify artist IDs to follow

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

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 behavioral burden. It says nothing about required auth/scopes, idempotency (following an already-followed artist), rate limits, or side effects on the user's profile — all relevant for a mutation tool.

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?

A single front-loaded sentence with zero filler. It is appropriately terse for the tool's simplicity, though the same brevity leaves gaps that a slightly longer description could close.

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?

For a mutation tool with no annotations and no output schema, the description is too thin: it omits auth requirements, effect on existing follows, and any indication of what is returned or how to verify success.

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?

The single parameter is fully documented in the schema (array of artist IDs, 1-50 items), and the description's 'one or more' aligns with the minItems/maxItems bounds. With 100% schema coverage the baseline of 3 is appropriate; the description adds no format or sourcing detail beyond the schema.

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 and resource ('Follow ... artists'), which is unambiguous. However it does no sibling differentiation: it never contrasts with spotify_unfollow_artists or spotify_get_followed_artists, leaving the agent to infer the follow/unfollow distinction.

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 guidance and no alternatives named, despite two closely related siblings (spotify_unfollow_artists, spotify_get_followed_artists). Usage is only vaguely implied by the verb.

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