Skip to main content
Glama
keenanbb

TIDAL MCP Server

by keenanbb

remove_album_from_favorites

Remove an album from your TIDAL favorites list by providing the album ID to manage your saved music collection.

Instructions

Remove an album from user's favorites.

Args: album_id: ID of the album to remove from favorites

Returns: Success status and confirmation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
album_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesOperation status (success/error)
item_idYesID of the item removed from favorites
messageYesStatus message
item_typeYesType of item (track/album/artist)

Implementation Reference

  • The @mcp.tool()-decorated handler function that executes the logic to remove an album from the user's TIDAL favorites using the tidalapi session.
    @mcp.tool()
    async def remove_album_from_favorites(album_id: str) -> RemoveFromFavoritesResult:
        """
        Remove an album from user's favorites.
    
        Args:
            album_id: ID of the album to remove from favorites
    
        Returns:
            Success status and confirmation
        """
        if not await ensure_authenticated():
            raise ToolError("Not authenticated. Please run the 'login' tool first.")
    
        try:
            album_id_int = int(album_id)
            await anyio.to_thread.run_sync(
                session.user.favorites.remove_album, album_id_int
            )
    
            return RemoveFromFavoritesResult(
                status="success",
                item_id=album_id,
                item_type="album",
                message=f"Album {album_id} removed from favorites",
            )
        except ValueError:
            raise ToolError(f"Invalid album ID format: {album_id}")
        except Exception as e:
            raise ToolError(f"Failed to remove album from favorites: {str(e)}")
  • Pydantic BaseModel defining the structured output schema for remove_album_from_favorites and similar tools, including status, item_id, item_type, and message.
    class RemoveFromFavoritesResult(BaseModel):
        """Result of removing an item from favorites."""
    
        status: str = Field(description="Operation status (success/error)")
        item_id: str = Field(description="ID of the item removed from favorites")
        item_type: str = Field(description="Type of item (track/album/artist)")
        message: str = Field(description="Status message")
  • The @mcp.tool() decorator registers this function as an MCP tool named 'remove_album_from_favorites' with FastMCP.
    @mcp.tool()
    async def remove_album_from_favorites(album_id: str) -> RemoveFromFavoritesResult:
        """
        Remove an album from user's favorites.
    
        Args:
            album_id: ID of the album to remove from favorites
    
        Returns:
            Success status and confirmation
        """
        if not await ensure_authenticated():
            raise ToolError("Not authenticated. Please run the 'login' tool first.")
    
        try:
            album_id_int = int(album_id)
            await anyio.to_thread.run_sync(
                session.user.favorites.remove_album, album_id_int
            )
    
            return RemoveFromFavoritesResult(
                status="success",
                item_id=album_id,
                item_type="album",
                message=f"Album {album_id} removed from favorites",
            )
        except ValueError:
            raise ToolError(f"Invalid album ID format: {album_id}")
        except Exception as e:
            raise ToolError(f"Failed to remove album from favorites: {str(e)}")
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the action is a removal but doesn't disclose permissions needed, whether the change is reversible, rate limits, or what happens if the album isn't in favorites. The mention of 'Success status and confirmation' in Returns hints at output but lacks detail.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The Args and Returns sections are structured but could be more integrated; overall, it's efficient with minimal waste.

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 no annotations, 0% schema coverage, but an output schema exists, the description is moderately complete. It covers purpose and parameter semantics but lacks behavioral context and usage guidelines. For a mutation tool with siblings, more guidance on prerequisites and alternatives would improve completeness.

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

Parameters3/5

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

Schema description coverage is 0%, but the description compensates by explaining 'album_id: ID of the album to remove from favorites', adding meaning beyond the bare schema. However, it doesn't specify format (e.g., numeric vs. string) or constraints, leaving gaps. With one parameter, baseline is 4, but limited detail reduces score.

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 ('Remove') and resource ('album from user's favorites'), making the purpose immediately understandable. It distinguishes from siblings like 'remove_track_from_favorites' by specifying album rather than track, but doesn't explicitly contrast with other album-related tools like 'get_album' or 'search_albums'.

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?

No guidance is provided about when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., album must already be in favorites), nor does it reference sibling tools like 'get_favorite_albums' for checking favorites first or 'remove_track_from_favorites' for different resource types.

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