@striderlabs/mcp-spotify

create_playlist

Create a new playlist in your Spotify account by providing a name and optional description and public visibility. Returns the new playlist's ID and URI.

Instructions

Create a new playlist in your Spotify account. Returns the new playlist ID and URI.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_playlist"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name for the new playlist
`public`	No	Whether the playlist should be public (default: false)
`description`	No	Optional description for the playlist

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full transparency burden. It discloses the mutation effect and return values, but does not mention authentication requirements, permission expectations, or potential side effects beyond creating the playlist. This is adequate but leaves gaps.

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 with the verb and resource front-loaded, no filler, and no redundant statements. Every word earns its place.

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

Completeness4/5

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

For a simple three-parameter create tool with fully described schema and clear return values, the description is substantially complete. It lacks only broader context like auth prerequisites or relationship to other playlist tools, but those are inferable from sibling names.

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?

Input schema description coverage is 100%, so the schema already documents all three parameters. The description adds no additional parameter semantics beyond naming the resource; it does not clarify default visibility or description formatting beyond what the schema provides.

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 opens with a specific verb and resource ('Create a new playlist in your Spotify account') and states the return value (playlist ID and URI). This clearly distinguishes it from sibling playback and playlist search tools.

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?

The action itself implies when to use it, but there is no explicit when-to-use guidance, no prerequisites such as authentication, and no mention of alternatives. Sibling tools like get_playlists and add_to_playlist are distinct enough that the absence is not fatal, but the guidance is minimal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.