Skip to main content
Glama
keenanbb

TIDAL MCP Server

by keenanbb

search_artists

Find artists on TIDAL by name to access their profiles, music, and related content. Specify search terms and result limits to discover matching performers.

Instructions

Search for artists on TIDAL.

Args: query: Search query - artist name limit: Maximum results (1-50, default: 10)

Returns: List of matching artists with id, name, and URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of artists returned
queryNoSearch query used (for search results)
statusYesOperation status (success/error)
artistsYesList of artist objects

Implementation Reference

  • The main handler function for the 'search_artists' tool, which performs the artist search using tidalapi and returns structured ArtistList.
    @mcp.tool()
    async def search_artists(query: str, limit: int = 10) -> ArtistList:
        """
        Search for artists on TIDAL.
    
        Args:
            query: Search query - artist name
            limit: Maximum results (1-50, default: 10)
    
        Returns:
            List of matching artists with id, name, and URL
        """
        if not await ensure_authenticated():
            raise ToolError("Not authenticated. Please run the 'login' tool first.")
    
        try:
            limit = min(max(1, limit), 50)
            results = await anyio.to_thread.run_sync(
                lambda: session.search(query, models=[tidalapi.Artist], limit=limit)
            )
    
            artists = []
            for artist in results.get("artists", []):
                artists.append(
                    Artist(
                        id=str(artist.id),
                        name=artist.name,
                        url=f"https://tidal.com/browse/artist/{artist.id}",
                    )
                )
    
            return ArtistList(status="success", query=query, count=len(artists), artists=artists)
        except Exception as e:
            raise ToolError(f"Artist search failed: {str(e)}")
  • Pydantic model defining the output schema for search_artists tool response.
    class ArtistList(BaseModel):
        """List of artists with metadata."""
    
        status: str = Field(description="Operation status (success/error)")
        query: Optional[str] = Field(None, description="Search query used (for search results)")
        count: int = Field(description="Number of artists returned")
        artists: List[Artist] = Field(description="List of artist objects")
  • Pydantic model for individual Artist objects used in ArtistList.
    class Artist(BaseModel):
        """Structured representation of a TIDAL artist."""
    
        id: str = Field(description="Unique TIDAL artist ID")
        name: str = Field(description="Artist name")
        url: str = Field(description="TIDAL web URL for the artist")
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the service (TIDAL) and return format, but lacks critical behavioral details: whether this requires authentication, rate limits, pagination behavior, or error conditions. The description doesn't contradict annotations since none exist, but it's insufficient for a tool with no annotation coverage.

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?

Perfectly structured and concise: purpose statement followed by clear Args and Returns sections. Every sentence earns its place - no wasted words. The information is front-loaded with the core purpose first.

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?

Given the tool has an output schema (though not shown here), the description doesn't need to fully explain return values. It provides adequate context for a search tool: service, parameters, and return format overview. However, with no annotations and behavioral gaps, it's not fully complete for a tool that might have authentication or rate limiting requirements.

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 description coverage, the description fully compensates by documenting both parameters thoroughly. It explains 'query' is for artist name searching and 'limit' has a range (1-50) with default value 10 - information not present in the bare schema. This adds significant value beyond the minimal schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search for artists on TIDAL' which is a specific verb+resource combination. It distinguishes from siblings like search_albums and search_tracks by specifying the artist domain, though it doesn't explicitly contrast with get_artist which retrieves a specific artist rather than searching.

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

Usage Guidelines3/5

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

The description implies usage through the 'Search for artists' phrase, suggesting it's for finding artists by name. However, it doesn't provide explicit guidance on when to use this versus alternatives like get_artist (for known IDs) or search_albums/tracks (for other content types). No exclusions or prerequisites are mentioned.

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

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