Skip to main content
Glama

playlist-list

Read-onlyIdempotent

List the world's playlists (mode, channel, sound count, what is playing), or one playlist with its sounds when playlistId is given. Requires bridge module 8.19.0+.

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": "playlist-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistIdNoPlaylist ID (from this tool) — returns its sounds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the version prerequisite and the specific fields returned in list mode. It omits return shape for single-playlist mode and any notion of list size or 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?

One tightly written sentence with the default behavior, the field summary, the parameter-driven alternative, and the version requirement in that order. Nothing is redundant or padded.

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 one-optional-parameter read tool with full annotation coverage, this is nearly complete: it explains both modes, the prerequisite, and partial return contents. The only remaining gap is guidance on result volume or ordering for the world-list mode, which an agent might care about with no output schema present.

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 100% and the schema already documents playlistId as 'Playlist ID (from this tool) — returns its sounds'. The description's 'or one playlist with its sounds when playlistId is given' largely restates that, so the baseline of 3 applies rather than a higher score.

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?

The description names a specific verb and resource ('List the world's playlists') and explicitly covers both operating modes: a full list with its returned fields (mode, channel, sound count, what is playing) and a single-playlist-with-sounds mode when playlistId is given. An agent can immediately tell this apart from playlist-delete, playlist-play, and playlist-set.

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 clearly states the condition that selects single-playlist mode ('when playlistId is given') versus the default full-list mode, and adds a concrete prerequisite ('Requires bridge module 8.19.0+'). It stops short of saying when to prefer a different sibling tool, but the mode switch and version gate give an agent everything needed to choose correctly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources