Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_playlist

Update a Spotify playlist's name, description, public visibility, or collaborative setting. Provide playlist ID and new values to apply changes; use dry_run to preview.

Instructions

Update a playlist's name, description, or visibility

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for playlist_id
nameNoNew name
publicNoNew public state
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
descriptionNoNew description
playlist_idNoPlaylist ID
collaborativeNoNew collaborative state

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
    • changedInput schema / properties / id / description
      Previous value: -"Playlist ID"New value: +"Alias for playlist_id"
    • addedInput schema / properties / playlist_id
      Added value: +{
+  "description": "Playlist ID",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "id"
-]
  2. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Update' without explaining mutation semantics. It does not mention whether unspecified fields remain unchanged, whether changes are reversible, required permissions, or that dry_run is available for previewing a change.

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?

The description is a single focused sentence with no wasted words, and the primary action and resource are front-loaded. It loses a point for omitting the collaborative field and for not signaling important behavior like partial updates or dry_run.

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?

This is a 7-parameter mutation tool with no annotations and no output schema, but the description provides only a minimal summary. It does not clarify core behavioral questions such as whether only provided fields are updated, whether both id and playlist_id are interchangeable, or what happens when no optional field is supplied.

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%, so the parameter descriptions already document each field, including dry_run and the id/playlist_id alias. The tool description adds little beyond naming three of the supported fields and does not clarify the update semantics for collaborative or the alias relationship beyond what the schema already provides.

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?

The description clearly identifies the action (update) and resource (a playlist), specifying three updatable aspects: name, description, and visibility. It is distinguishable from siblings like create_playlist or reorder_playlist_items, though it omits the collaborative field that the schema also supports, slightly limiting completeness.

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 guidance is provided about when to use this tool versus alternatives such as reorder_playlist_items, replace_playlist_items, upload_playlist_cover, or create_playlist. The description does not state that this is for metadata-only updates or mention prerequisites like owning the playlist.

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