Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

playlist_tracks

Lists tracks in an owned or collaborative Spotify playlist by name, ID, URI, or URL, with an optional limit for inspecting playlist contents.

Instructions

List the tracks of one playlist (by name, id, spotify: URI or open.spotify.com URL). Only playlists the user owns or collaborates on are readable.

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>"
    },
    "name": "playlist_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax tracks to return (default 100)
playlistYesPlaylist name (partial ok), id, URI or URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/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 burden but does disclose a real behavioral constraint: only owned or collaborated playlists are readable, which signals a permission scope failure mode. It omits other important behavior — what happens when a partial name matches multiple playlists, whether results are ordered, and whether a 500-capped limit implies truncation.

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 short sentences, zero filler. The primary action and identifier formats come first, with the access constraint second — well front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with no output schema and no annotations, this covers the essentials: what it returns, valid identifiers, and the access limitation. The remaining gap is edge-case behavior (ambiguous partial names, truncation when limit is hit), which keeps it just short of complete.

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 both parameters are already documented, including the default of 100. The description restates the accepted playlist identifier forms (name, id, URI, URL) but adds nothing about partial-name resolution or limit semantics beyond the schema, so baseline 3 applies.

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 opens with a specific verb and resource: 'List the tracks of one playlist' — clearly distinct from list_playlists and add_to_playlist in scope. It never names or contrasts a sibling tool, so differentiation is inherent rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied by the resource: an agent can infer 'call this when you need the contents of a single playlist.' The second sentence is a precondition (ownership/collaboration), not when-to-use guidance, and no alternative for searching across playlists is mentioned.

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