Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_playlist

Change a playlist's name, description, visibility, or collaborative state to keep it accurate and private.

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. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
-]
  3. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations only say destructiveHint=false, and the description adds no behavioral context beyond that: it does not state that changes are partial, that dry_run previews without performing, or how the API treats omitted fields. The description mostly restates the tool's name and schema fields.

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?

One front-loaded sentence with no filler, which is efficient. It loses a point because 'visibility' is ambiguous relative to the actual boolean fields and collaborative is omitted without any structural payoff.

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 seven optional parameters, no output schema, and only a destructiveHint annotation, this is under-specified. It fails to mention the dry_run preview option, leaves collaborative out, and gives no selection rule among numerous playlist mutators, so an agent gets little help beyond the schema.

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 baseline is 3 and the schema already documents each parameter. The description adds no new parameter meaning and even calls the public field 'visibility' while omitting collaborative; however, the schema's per-parameter descriptions carry the needed semantics.

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?

Begins with a specific verb ('Update') and names the resource ('a playlist') plus the affected fields (name, description, visibility), so the basic purpose is clear. It does not differentiate against sibling playlist tools such as create_playlist, playlist_sort, or add_to_playlist, and 'visibility' maps only loosely to the schema's public/collaborative booleans.

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 sentence explains when to use this tool instead of the many playlist-editing siblings, and there are no exclusions or alternatives. The only guidance is implied by the verb 'Update,' which does not help choose between update_playlist, playlist_reverse, playlist_trim, or remove_from_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