Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_playlist

Create a new playlist for the current Spotify user. Use dry_run mode to preview changes before actually creating the playlist.

Instructions

Create a new playlist for the current user. Set dry_run=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPlaylist name
publicNoWhether the playlist is public. Default: false
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
descriptionNoPlaylist description
collaborativeNoWhether the playlist is collaborative. Default: false

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. Changed2 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"
+}
  3. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=false, so the description need not restate safety. It adds the dry_run preview behavior, which is a useful nuance. However, it doesn't disclose other behavioral aspects like required authentication, rate limits, or the result payload on success. Since the create operation is inherently mutating but safe, the description provides moderate additional context beyond annotations.

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 convey both the primary function and a key usage tip without any filler. The description is front-loaded with the core action and includes the dry_run hint efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a simple create operation with five documented parameters, but there is no output schema and the description doesn't mention what the tool returns (e.g., the created playlist object). Given the complexity is low and the schema covers inputs, this is adequate but leaves the return behavior unspecified. No prerequisites or side effects are described beyond dry_run.

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 all five parameters are documented in the schema. The description mentions dry_run, which reinforces the schema's description but doesn't add new meaning. It doesn't clarify any parameter semantics beyond what's already in the schema, so the baseline score of 3 is appropriate.

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?

Description states a specific verb ('Create') and resource ('a new playlist for the current user'), which clearly distinguishes it from read-only or update operations. It is concise and unambiguous, though it does not explicitly contrast with sibling 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 Guidelines2/5

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

No guidance is given on when to prefer this tool over alternatives like update_playlist or add_to_playlist. The only usage hint is the dry_run flag for preview, but there is no explicit condition for when to use or avoid this tool.

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