Skip to main content
Glama
raydollete

TIDAL Music MCP

by raydollete

create_playlist_from_songs

Creates a TIDAL playlist by searching for songs from descriptions and adding best matches, reporting match rate and unmatched songs.

Instructions

Creates a TIDAL playlist by searching for songs and adding the best matches.
This is the RECOMMENDED way to create a playlist when you have song names/descriptions.

USE THIS TOOL WHEN:
- A user provides a list of song names to add to a playlist
- You need to create a playlist from song descriptions (not track IDs)
- You want to build a playlist based on user-provided song names

This tool handles the entire workflow efficiently:
1. Batch search for all songs concurrently
2. Collect the best matching track IDs
3. Create the playlist with all found tracks

This is MUCH faster than searching for songs one-by-one and then creating a playlist.

Args:
    title: Name for the new playlist
    song_descriptions: List of song descriptions to search for.
                      Include artist name for better matching.
                      Examples: ["Bohemian Rhapsody by Queen", "Yesterday Beatles",
                                "Stairway to Heaven Led Zeppelin"]
                      Maximum 100 songs per request.
    description: Optional playlist description

Returns:
    Dictionary with:
    - playlist: Created playlist details including URL
    - matched_songs: List of songs that were found with their track info
    - unmatched_songs: List of songs that couldn't be found
    - match_rate: e.g., "45/50" showing how many songs were matched

Example:
    create_playlist_from_songs(
        title="My 80s Favorites",
        song_descriptions=[
            "Take On Me a-ha",
            "Livin' on a Prayer Bon Jovi",
            "Sweet Child O' Mine Guns N' Roses"
        ],
        description="Classic 80s hits"
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
descriptionNo
song_descriptionsYes
Behavior4/5

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

No annotations provided, so description carries full burden. It describes the workflow (batch search, collect matches, create playlist), maximum 100 songs per request, and the return structure. However, it does not mention potential side effects (e.g., overwriting existing playlists) or required permissions. Still, it's fairly transparent about behavior.

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 well-structured with sections (purpose, when-to-use, workflow, args, returns, example). It is slightly verbose but every part adds value. Front-loaded with the main verb and resource. Could trim minor redundancy but overall efficient.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description provides comprehensive context: return dictionary details (playlist, matched_songs, unmatched_songs, match_rate), workflow steps, example usage, and limitations (max 100 songs). It fully compensates for the lack of structured documentation.

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 coverage is 0% (no property descriptions in schema), but the description adds an 'Args' block detailing each parameter: title as 'Name for the new playlist', song_descriptions with examples and max 100, description as optional. This adds significant meaning beyond the bare 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?

The description clearly states the tool creates a TIDAL playlist by searching for songs and adding best matches. It distinguishes from siblings like 'create_tidal_playlist' (which likely creates empty playlists) and 'add_tracks_to_playlist' (which adds tracks by ID). The verb 'create' and resource 'playlist from songs' are specific.

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

Usage Guidelines5/5

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

Explicit 'USE THIS TOOL WHEN:' section lists three scenarios (song names, descriptions, building from names). Implicitly tells when not to use (when track IDs are available). Also notes it's faster than alternatives like searching one-by-one then creating. Provides clear context.

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

Install Server

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/raydollete/tidal-dl-mcp'

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