Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

create_playlist

Create a new private Spotify playlist by name, optionally set it public with a description, and return its ID and URL.

Instructions

Create a new playlist in the user's account (private by default). Returns its id and URL.

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

NameRequiredDescriptionDefault
nameYesPlaylist name
publicNoMake it public (default false)
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose two useful behaviors: playlists are private by default, and the response contains id and URL. It omits mutation-relevant context such as required auth/account scope, behavior on duplicate names, and whether creation is reversible — significant gaps 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 tight sentences with no filler; the core action is front-loaded and the default-visibility note follows immediately. Every clause earns its place.

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 3-parameter mutation with no output schema, the description helpfully states what is returned (id and URL) and the default visibility. However, a write tool with no annotations should also cover auth requirements and side effects, which are absent.

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 coverage is 67%, and the description adds real meaning for one parameter by explaining that playlists are private by default, which clarifies the `public` flag's default semantics. It says nothing about the `name` or `description` parameters, so the remaining 33% gap is not compensated for.

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 playlist") plus the scope ("in the user's account"), which is enough to distinguish it from add_to_playlist or list_playlists. It stops short of explicitly naming a sibling, so it lands at 4 rather than 5.

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?

The description offers no when-to-use, when-not-to-use, or alternative guidance at all — nothing tells the agent how this differs from add_to_playlist or when creating a playlist is the right move. The operation is largely self-evident from the name, but the definition itself contributes no routing logic.

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