Skip to main content
Glama
raydollete

TIDAL Music MCP

by raydollete

batch_search_tidal

Search TIDAL for multiple tracks, albums, or artists in one request. Batch process up to 100 queries to reduce API calls and speed up data retrieval.

Instructions

Search TIDAL for multiple tracks/albums/artists in a single request.
This is MUCH MORE EFFICIENT than calling search_tidal multiple times.

USE THIS TOOL WHEN:
- You need to search for multiple songs to create a playlist
- You have a list of song names to look up
- You're building a collection of tracks based on a user's description
- The user provides a list of songs they want to find

This tool processes all searches concurrently, making it 10-50x faster than
calling search_tidal repeatedly for each song.

When processing the results:
1. Check each result for the 'tracks' array with matching songs
2. Use the first track in each result as the best match
3. Some queries may have 'error' instead of results - handle gracefully
4. Collect track IDs for playlist creation

Args:
    queries: List of search queries. Each item can be:
             - A string: "Bohemian Rhapsody Queen" (searches for tracks)
             - A dict with 'query' and optional 'type':
               {"query": "Bohemian Rhapsody", "type": "track"}
             Valid types: "track", "album", "artist", "playlist", "all"
             Default type is "track" if not specified.
             Maximum 100 queries per request.
    limit_per_query: Maximum results per query (default: 5, max: 20)
                    Keep this low (1-5) for faster responses when you only need the best match.

Returns:
    Dictionary with 'results' array containing search results for each query.
    Each result includes the original query and matching tracks/albums/etc.

Example:
    batch_search_tidal([
        {"query": "Bohemian Rhapsody Queen", "type": "track"},
        {"query": "Yesterday Beatles", "type": "track"},
        "Stairway to Heaven"  # String queries default to track type
    ], limit_per_query=1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queriesYes
limit_per_queryNo
Behavior5/5

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

Discloses concurrency, 10-50x speedup, maximum 100 queries, and expected result structure including error handling. No annotations present, so description fully compensates.

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?

Well-organized with sections for overview, usage, processing steps, and parameter details. No redundant sentences; every sentence adds value.

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?

Despite no output schema, description fully explains return structure, how to interpret results, and error handling. Covers all necessary context for an AI agent to use the tool effectively.

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?

With 0% schema coverage, description extensively explains both parameters: queries can be strings or dicts with type options, limit_per_query with default and max, plus an example showing usage.

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?

Clearly states it searches TIDAL for multiple items in a single request, explicitly contrasting with the less efficient search_tidal. Verb 'search' and resource 'TIDAL' 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?

Provides explicit 'USE THIS TOOL WHEN' list with concrete scenarios, and implies when not to use by comparing efficiency with sibling search_tidal.

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