Create a new Spotify playlist by providing a name, and optionally set its description and public visibility. Use it to organize tracks into a new playlist for playback or sharing.
Create a new playlist
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Playlist name | |
| public | No | Whether the playlist should be public (default: true) | |
| description | No | Playlist description |
Changes observed during successful MCP inspections.
v1.2.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the mutation and never mentions authentication requirements, that the playlist is added to the user's library, or any side effects, leaving the mutation semantics largely unexplained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than efficient conciseness given the gaps elsewhere.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description should cover permissions, defaults, and return behavior. It covers none of these, leaving an agent under-informed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% (name, public, description all documented), so the baseline of 3 applies. The description adds no meaning beyond the schema's parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource (create a playlist), so the operation is unambiguous. It does not, however, differentiate itself from siblings such as spotify_update_playlist or spotify_delete_playlist, which act on the same resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives, nor any preconditions mentioned. An agent must infer everything from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.