Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

add_to_playlist

Add Spotify tracks or episodes to a playlist you own or collaborate on using track or episode URIs; append them in order or insert at a chosen position.

Instructions

Add tracks to a playlist the user owns or collaborates on, by spotify:track: URIs (resolve names first with search). Appends in order unless a position is given.

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": {
      "playlist": "<playlist>",
      "uris": "<uris>"
    },
    "name": "add_to_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
urisYesspotify:track:... or spotify:episode:... URIs
playlistYesPlaylist name (partial ok), id, URI or URL
positionNo0-based insert position (default: append)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses permission constraints (owner/collaborator), the URI-only input requirement, and append ordering with position override, but says nothing about duplicate handling, failure modes, or what a successful call returns.

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, front-loaded with the action and its precondition, then the ordering behavior. Nothing is redundant and no sentence could be removed without losing meaning.

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?

Adequate for a 3-parameter mutation tool with no annotations and no output schema: it covers permissions, input format, and ordering. It omits error behavior and post-call results, leaving meaningful gaps for a write operation that returns no schema.

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 all three parameters are already documented, which sets the baseline at 3. The description adds modest value by explaining default append ordering versus an explicit position and by directing name resolution to `search`, but adds no syntax or format details beyond the schema.

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?

States a specific verb (add tracks), the resource (a playlist), and the ownership constraint ('the user owns or collaborates on'), plus the required URI format. It also names the prerequisite step ('resolve names first with `search`'), which cleanly separates it from the search sibling.

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?

Gives clear preconditions: the playlist must be owned or collaborated on, and track names must be resolved via `search` first. It does not state explicit when-not conditions or what to do if the playlist isn't found/writable, so it falls short of a 5.

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