Skip to main content
Glama
yuhuacheng

TIDAL MCP: My Custom Picks

tidal_login

Authenticate with TIDAL by opening a browser window for secure login, enabling access to personalized music recommendations and playlist creation.

Instructions

Authenticate with TIDAL through browser login flow.
This will open a browser window for the user to log in to their TIDAL account.

Returns:
    A dictionary containing authentication status and user information if successful

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tidal_login tool handler function, registered via @mcp.tool() decorator. It handles authentication by calling the backend Flask API at /api/auth/login and returns success or error status with user info.
    @mcp.tool()
    def tidal_login() -> dict:
        """
        Authenticate with TIDAL through browser login flow.
        This will open a browser window for the user to log in to their TIDAL account.
        
        Returns:
            A dictionary containing authentication status and user information if successful
        """
        try:
            # Call your Flask endpoint for TIDAL authentication
            response = requests.get(f"{FLASK_APP_URL}/api/auth/login")
            
            # Check if the request was successful
            if response.status_code == 200:
                return response.json()
            else:
                error_data = response.json()
                return {
                    "status": "error",
                    "message": f"Authentication failed: {error_data.get('message', 'Unknown error')}"
                }
        except Exception as e:
            return {
                "status": "error",
                "message": f"Failed to connect to TIDAL authentication service: {str(e)}"
            }
  • The @mcp.tool() decorator registers the tidal_login function as an MCP tool.
    @mcp.tool()
  • Function signature and docstring defining the tool's schema: no input parameters, returns a dict with authentication status and optional user information.
    def tidal_login() -> dict:
        """
        Authenticate with TIDAL through browser login flow.
        This will open a browser window for the user to log in to their TIDAL account.
        
        Returns:
            A dictionary containing authentication status and user information if successful
        """
Behavior3/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 describes the action (opens a browser window) and return value (dictionary with auth status and user info), which covers basic behavior. However, it lacks details on error handling, timeouts, or what happens if the user cancels the login, leaving gaps in transparency for an authentication tool.

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 concise and well-structured: two sentences that clearly state the action and the return value, with no wasted words. It's front-loaded with the main purpose. A minor deduction because it could be slightly more efficient by combining ideas, but overall it's very effective.

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 complexity of an authentication tool with no annotations and no output schema, the description is moderately complete. It covers the core action and return value, but lacks details on prerequisites (e.g., browser availability), side effects, or error cases. For a tool that interacts with external systems, more context would be beneficial to ensure safe and correct usage.

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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics beyond the schema, but it correctly notes no inputs are required. Baseline is 4 for 0 parameters, as it appropriately handles the absence of parameters without redundancy.

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 tool's purpose: 'Authenticate with TIDAL through browser login flow.' It specifies the verb (authenticate) and resource (TIDAL) with the mechanism (browser login flow). However, it doesn't explicitly differentiate from sibling tools, which are all data retrieval/manipulation tools rather than authentication tools, so it doesn't fully address sibling differentiation.

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 context by mentioning 'browser login flow' and returning authentication status, suggesting this tool should be used to establish a session before other TIDAL operations. However, it doesn't explicitly state when to use it versus alternatives (e.g., if there are other auth methods) or provide clear exclusions, leaving some ambiguity.

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

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