Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

list_playlists

Retrieve owned and followed Spotify playlists with IDs, owners, track counts, and whether tracks are readable. Use this to identify playlists that can be inspected or exported.

Instructions

List the user's Spotify playlists (owned and followed) with id, owner, track count and whether their tracks are readable (owned or collaborative).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/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 usefully discloses returned fields and that readability is limited to owned or collaborative playlists, but it omits authentication requirements, pagination behavior, and result ordering.

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?

The description is a single, front-loaded sentence with no wasted wording. It efficiently packs scope, returned fields, and the readability caveat into one clear statement.

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 zero-parameter read tool with no annotations or output schema, the description explains what is included and what fields are returned. It is largely complete, though it could mention pagination, ordering, or authentication prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero input parameters, so parameter semantics baseline is 4. The description adds no parameter guidance because none exist, and nothing is missing on this dimension.

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, 'List', and resource, 'the user's Spotify playlists', with scope (owned and followed) and returned fields (id, owner, track count, readability). It is clear but does not explicitly distinguish itself from the sibling tool export_playlists, so it falls short of a 5.

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?

The description implies the use case of getting a playlist inventory, but it gives no explicit when-to-use guidance or alternatives. It does not mention export_playlists, playlist_tracks, or other sibling tools, leaving usage context only implied.

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