Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_playlist

Create a new Spotify playlist for the current user. Set name, description, public or collaborative options, or use dry-run mode to preview changes before creating.

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

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description bears the full behavioral disclosure burden. It does disclose that the operation creates (a mutation), targets the current user's account, and offers a dry_run preview that avoids side effects — genuinely useful safety context. However, it doesn't address auth requirements, reversibility, rate limits, or what the operation returns, which is meaningful for a write operation with zero annotation coverage.

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 with zero waste. The core purpose is front-loaded in the first sentence, and the second sentence earns its place by flagging the dry_run safety valve. No redundant phrasing, no restatement of schema defaults.

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?

For a simple create tool the description covers the purpose and the safety valve adequately, and the schema documents all parameters. The notable gap is the return value — with no output schema, an agent doesn't know the tool returns the created playlist (presumably with ID/URI), which matters for chaining into add_to_playlist or update_playlist. This is a real but non-fatal omission.

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 schema already documents all five parameters (name, public, dry_run, description, collaborative) with default values. The description adds no parameter syntax or format detail beyond the schema; it only re-mentions dry_run, which the schema already explains. This lands at the baseline 3 for high-coverage schemas.

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 specific verb ('Create'), a resource ('a new playlist'), and a scope ('for the current user'). This clearly separates it from update_playlist (modify), copy_playlist (duplicate), and import_playlist (import existing), all of which appear in the sibling list. The added dry_run sentence further sharpens what the tool does by revealing a preview mode.

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?

Usage is implied rather than stated: the description makes clear this is the tool for creating a new playlist, but it never explicitly contrasts with near-neighbors like create_smart_playlist, copy_playlist, or playlist_to_library. The dry_run=true hint does give practical usage context for previewing before committing, but no when-not-to-use guidance is present.

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