Spotify & TMDB Web MCP Server

Overview Schema Source Related Servers Discussions Admin

create_playlist

Create a new Spotify playlist with a name, optional description, and public or private visibility to organize and share selected tracks.

Instructions

Create a new Spotify playlist for the user.

Args: name: Name of the playlist description: Description of the playlist public: Whether the playlist is public (default: True)

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	Default
`name`	Yes
`public`	No
`description`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive, open-world write, so the safety profile is covered. The description adds only that the playlist belongs to "the user" and that public defaults to True; it says nothing about authorization scopes, whether duplicate names are allowed, or what happens if creation fails, which is the kind of context annotations cannot express.

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 summary sentence followed by a short Args list; nothing is padded or rambling. The Args block partially duplicates schema titles, but it is compact and front-loaded.

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 three-parameter creation tool with an output schema (so return values need not be explained), the description is adequate but thin. It omits the authentication requirement and any note on how this differs from the actor-playlist sibling, which an agent needs to pick correctly.

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 0%, so the description carries the burden, and it does enumerate all three parameters via an Args block. However, the mappings are near-tautological ("name: Name of the playlist") and the public default is already in the schema, so little meaning is added beyond labels.

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?

States a specific verb and resource ("Create a new Spotify playlist") plus the owner scope ("for the user"), so the action is unambiguous. It does not differentiate from the sibling create_actor_playlist, which also creates a playlist, leaving the agent to guess which one applies.

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?

There is no when-to-use guidance, no prerequisites (e.g. authenticated user required), and no mention of the closely related alternatives such as create_actor_playlist or add_tracks_to_playlist that would naturally follow. The agent must infer the workflow entirely.

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

Deploy Server