Skip to main content
Glama
Sign In
lyricmood-mcp

lyricmood-mcp

by yigitates17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Spotify Playlist

create_spotify_playlist

Create a private or public Spotify playlist from track IDs, URLs, or URIs in order, with an optional description, once the user confirms the name and track list.

Instructions

Create a new playlist in the user's Spotify account (private unless public is true) and add the given tracks in order. This changes the user's account: only call it after the user has agreed to the name and the track list.

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_spotify_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPlaylist name.
publicNoFalse (default) keeps it private to the user.
tracksNoSpotify track IDs, URLs or URIs (use `id` from search_track or build_mood_playlist). Song names are not accepted here.
descriptionNoOptional description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 load and does disclose the key traits: it mutates the user's account, defaults to private unless `public` is true, preserves track order, and requires user consent. It omits what a mutation caller would want next — what is returned (a playlist ID for follow-up calls), duplicate-name behavior, and any failure modes.

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, zero filler. The side effect and default visibility come first, and the consent precondition is front-loaded as an imperative constraint the agent can act on.

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 mutation tool with no annotations and no output schema, the definition covers safety and privacy but leaves the return value undefined, which matters because a created playlist's identifier is typically needed for later calls. It is adequate to call the tool but not fully self-sufficient.

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 baseline is 3 and the schema already documents all four fields. The description adds only the ordering guarantee for `tracks` and the private-by-default consequence of `public`, both of which are largely mirrored in the schema.

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?

The description names a specific verb and resource ("Create a new playlist in the user's Spotify account") plus the side effect of adding tracks in order. It clearly separates creation from the sibling update_spotify_playlist, but it never distinguishes itself from build_mood_playlist, which also produces playlists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives an explicit precondition — "only call it after the user has agreed to the name and the track list" — which tells the agent when it may fire. It stops short of naming alternatives (build_mood_playlist for generated playlists, update_spotify_playlist for edits), so the routing guidance is incomplete rather than absent.

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