Skip to main content
Glama
raydollete

TIDAL Music MCP

by raydollete
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

download_favorites

Downloads all favorites from TIDAL, including tracks, albums, artists, or videos. Requires tidal-dl-ng installation and authentication.

Instructions

Downloads all favorites of a specific type from TIDAL using tidal-dl-ng.

USE THIS TOOL WHENEVER A USER ASKS FOR:
- "Download all my favorite tracks"
- "Download my saved albums"
- "Save all my favorites to my computer"
- "Download my favorite artists' music"
- Any request to download their saved/favorite content from TIDAL

IMPORTANT PREREQUISITES:
1. tidal-dl-ng must be installed: pip install tidal-dl-ng
2. User must have authenticated tidal-dl-ng: run 'tdn login' in terminal
3. tidal-dl-ng authentication is SEPARATE from TIDAL MCP authentication

When processing the results of this tool:
1. Confirm the download was started/completed or explain any errors
2. Warn user that downloading all favorites can take a VERY long time
3. If tidal-dl-ng is not installed, guide user to install it
4. If authentication failed, guide user to run 'tdn login' in terminal
5. The files will be saved to tidal-dl-ng's configured download location

Args:
    favorite_type: Type of favorites to download. One of:
                  - "tracks" (default) - Download all favorite tracks
                  - "albums" - Download all favorite albums
                  - "artists" - Download all content from favorite artists
                  - "videos" - Download all favorite videos

Returns:
    A dictionary containing download status and any output messages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
favorite_typeNotracks

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Discloses external dependency (tidal-dl-ng), separate authentication, long download times, and file save location. No annotations provided, so description carries full burden. Minor omission: no mention of disk space or cancellation 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?

Well-structured with sections and bullet points, but slightly verbose with repeated examples. Front-loaded purpose and guidelines effectively.

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?

Covers installation, authentication, expected behavior, result handling, and time expectations. Adequate for a tool with external dependencies and no output schema.

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?

Single parameter (favorite_type) fully explained with values and effects. Schema coverage 0% but description adds complete semantics beyond the basic schema definition.

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 it downloads all favorites of a specific type from TIDAL using tidal-dl-ng. It distinguishes from sibling tools like download_album, download_playlist, and download_track, which operate on individual items.

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?

Explicitly lists user requests that should trigger this tool (e.g., 'Download all my favorite tracks'). Provides prerequisites and warnings, and mentions error handling steps.

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