Skip to main content
Glama
keenanbb

TIDAL MCP Server

by keenanbb

get_favorite_artists

Retrieve a user's followed artists from TIDAL music service to access their favorite musicians and build personalized music experiences.

Instructions

Get user's favorite (followed) artists from TIDAL.

Args: limit: Maximum artists to retrieve (default: 50)

Returns: List of followed artists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 'get_favorite_artists' tool. It fetches the user's followed artists from TIDAL using the tidalapi library, authenticates if needed, and returns a structured ArtistList.
    @mcp.tool()
    async def get_favorite_artists(limit: int = 50) -> ArtistList:
        """
        Get user's favorite (followed) artists from TIDAL.
    
        Args:
            limit: Maximum artists to retrieve (default: 50)
    
        Returns:
            List of followed artists
        """
        if not await ensure_authenticated():
            raise ToolError("Not authenticated. Please run the 'login' tool first.")
    
        try:
            favorites = await anyio.to_thread.run_sync(
                lambda: session.user.favorites.artists(limit=limit)
            )
    
            artists = []
            for artist in favorites:
                artists.append(
                    Artist(
                        id=str(artist.id),
                        name=artist.name,
                        url=f"https://tidal.com/browse/artist/{artist.id}",
                    )
                )
    
            return ArtistList(status="success", count=len(artists), artists=artists)
        except Exception as e:
            raise ToolError(f"Failed to get favorite artists: {str(e)}")
  • Pydantic model defining the structured output schema returned by the get_favorite_artists tool, including status, count, and list of Artist objects.
    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")
  • Base Pydantic model for individual Artist objects used within 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")
  • Tool description in the server instructions docstring, which serves as informal registration documentation listing all available tools.
    - get_favorite_artists: Get your followed artists
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it retrieves data ('Get'), implying a read-only operation, but doesn't clarify authentication requirements, rate limits, pagination behavior, or error handling. The mention of a default limit is helpful but insufficient for a tool with zero 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?

The description is efficiently structured with a clear purpose statement followed by 'Args' and 'Returns' sections. Each sentence adds value: the first defines the tool, the second explains the parameter, and the third describes the output. There is no redundant or verbose content.

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

Completeness3/5

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

Given the tool's low complexity (one optional parameter) and the presence of an output schema (which handles return values), the description is minimally complete. However, it lacks details on authentication, error cases, or behavioral constraints, which are important for a tool with no annotations. The parameter explanation helps, but overall coverage is basic.

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

Parameters4/5

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

The description adds meaningful context for the single parameter 'limit', explaining it as 'Maximum artists to retrieve' with a default value, which compensates for the 0% schema description coverage. This goes beyond the schema's basic type and default, providing practical usage information. With only one parameter, this is adequate.

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 the action ('Get') and resource ('user's favorite (followed) artists from TIDAL'), making the purpose immediately understandable. It distinguishes from siblings like 'get_favorite_albums' and 'get_favorite_tracks' by specifying the resource type (artists). However, it doesn't explicitly contrast with 'get_artist' or 'search_artists', which slightly limits differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_artist' (for specific artist details) or 'search_artists' (for broader queries). It mentions the resource but lacks context about prerequisites (e.g., user authentication) or typical use cases, leaving the agent to infer usage from the name alone.

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