Skip to main content
Glama
Sign In
mcp-spotify

mcp-spotify

by obrien-matthew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

follow_playlist

Save any Spotify playlist to your library by providing its ID or URI. Ideal for keeping playlists found through search or shared by others.

Instructions

Follow (save) a Spotify playlist to your library.

Accepts a playlist ID or URI. Use this to save playlists found via search or shared by others.

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": {
      "playlist_id": "<playlist_id>"
    },
    "name": "follow_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlist_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions accepting 'playlist ID or URI,' adding input flexibility. However, it does not disclose side effects like duplicate handling or required authentication.

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?

Two sentences, no wasted words, front-loaded with purpose. Every sentence adds value.

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?

Given the tool's simplicity and presence of an output schema, the description is mostly complete. It could mention duplicate behavior but is adequate for a save action.

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 has one required param (playlist_id, no description). The description adds value: 'Accepts a playlist ID or URI,' clarifying acceptable formats beyond the schema.

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 clearly states the action: 'Follow (save) a Spotify playlist to your library.' It specifies the resource (playlist) and distinguishes from unfollow_playlist and other playlist tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Use this to save playlists found via search or shared by others,' giving clear usage context. However, it does not mention when not to use it or alternatives.

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