Skip to main content
Glama
ibeal
by ibeal

get_playlist_tracks

Retrieve all tracks from a TIDAL playlist by providing its playlist ID. Supports pagination with limit and offset to fetch specific subsets of large playlists.

Instructions

Retrieves all tracks from a specified TIDAL playlist.

USE THIS TOOL WHENEVER A USER ASKS FOR:
- "Show me the songs in my playlist"
- "What tracks are in my [playlist name] playlist?"
- "List the songs from my playlist"
- "Get tracks from my playlist"
- "View contents of my TIDAL playlist"
- Any request to see what songs/tracks are in a specific playlist

This function retrieves tracks from a specific playlist in the user's TIDAL account.
By default, it fetches ALL tracks using automatic pagination. Supply a
limit and offset to retrieve a smaller page from a large playlist.
The playlist_id must be provided, which can be obtained from the get_user_playlists() function.

When processing the results of this tool:
1. Present the playlist information (title, description, track count) as context
2. List the tracks in a clear, organized format with track name, artist, and album
3. Include track durations where available
4. Mention the total number of tracks in the playlist
5. If there are many tracks, focus on highlighting interesting patterns or variety

Args:
    playlist_id: The TIDAL ID of the playlist to retrieve (required)
    limit: Maximum number of tracks to retrieve (default: None, meaning fetch all tracks)
    offset: Zero-based index of the first track to retrieve (default: 0)

Returns:
    A dictionary containing tracks plus total_track_count, has_more, and next_offset
    pagination metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
playlist_idYes
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it does so well: it discloses automatic pagination, the default fetch-all behavior, the effect of limit and offset, and the exact pagination metadata returned (total_track_count, has_more, next_offset). There are no hidden side effects or surprise behaviors left unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than necessary and contains some redundancy—the purpose is stated twice—but it is well structured with clear sections, front-loaded usage triggers, and parameter explanations. The processing instructions are extra but useful for downstream response formatting.

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

Completeness5/5

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

This tool has no output schema, yet the description documents the return dictionary, pagination metadata, and parameter semantics. It also provides a prerequisite workflow via get_user_playlists() and gives presentation guidance. An agent has everything needed to select, invoke, and interpret this tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate fully. It explains playlist_id as required and how to obtain it, describes limit as the maximum tracks with default None meaning fetch all, and defines offset as a zero-based index with default 0. This adds real meaning beyond the bare schema properties.

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 opens with a specific verb and resource: 'Retrieves all tracks from a specified TIDAL playlist.' It clearly distinguishes this from sibling tools by scoping to playlist tracks, and it even points to get_user_playlists() for obtaining the playlist_id, reinforcing what this tool is not.

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?

The description provides an explicit, highlighted list of user-phrase triggers and explains when to use limit/offset for large playlists. It does not explicitly state when NOT to use this tool or name sibling alternatives like get_favorite_tracks or get_mix_tracks, so it falls just short of full exclusion guidance.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ibeal/tidal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server