Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pin_playlist

Follow a Spotify playlist to save it to your library; this deprecated action previews with dry_run and executes with dry_run:false. Use follow_playlist instead.

Instructions

DEPRECATED, use follow_playlist. This tool never pinned anything; it has always saved the playlist to your Spotify library via PUT /me/library.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
publicNoMust be true or omitted; the library endpoint has no visibility parameter.
dry_runNoPreview only (default): pass dry_run: false to execute the follow.
playlist_idYesPlaylist ID to follow
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
dry_runNo
receiptNo
cancelledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "cancelled": {
+      "type": "boolean"
+    },
+    "dry_run": {
+      "type": "boolean"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "receipt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changedv2.1.2
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": true,
+  "description": "Preview only (default): pass dry_run: false to execute the follow.",
+  "type": "boolean"
+}
    • changedInput schema / properties / public / description
      Previous value: -"Whether the follow should be public (Spotify default: true)"New value: +"Must be true or omitted; the library endpoint has no visibility parameter."
  3. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  4. Addedv1.26.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only cover destructiveHint=false, and the description adds real behavioral context: the tool never actually pins, the underlying endpoint is PUT /me/library, and it is deprecated. It does not discuss auth/scopes or idempotency, but for a deprecated alias the disclosure is strong.

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 short sentences, deprecation and the correct behavior front-loaded, zero filler. Every clause 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?

An output schema exists so return values need no explanation, and all four parameters are fully described in the schema. The description completes the picture by explaining the misleading name and the correct alternative.

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% and each parameter (public, dry_run, playlist_id, response_format) is documented in the schema itself. The description adds no parameter-level detail, so baseline 3 applies.

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 states a precise verb+resource ('saves the playlist to your Spotify library via PUT /me/library') and explicitly corrects the misleading name, so an agent knows exactly what it does. It also names the intended replacement (follow_playlist), distinguishing it from siblings.

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

Usage Guidelines5/5

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

It gives explicit when-not-to-use guidance ('DEPRECATED, use follow_playlist') and names the alternative tool by name. Nothing about selection is left to inference.

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