Skip to main content
Glama

get_queue

Retrieve the current list of tracks waiting to play in Spotify, showing upcoming songs in your playback queue.

Instructions

Get the current queue of tracks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:123-127 (handler)
    MCP FastMCP tool handler for 'get_queue'. This is the entrypoint registered with the MCP server, delegating to the SpotifyClient instance.
    @mcp.tool()
    async def get_queue() -> str:
        """Get the current queue of tracks"""
        return await client.get_queue()
  • Core implementation of get_queue in SpotifyClient class, calling the Spotipy API's queue() method to fetch the current playback queue.
    async def get_queue(self) -> dict:
        """
        Get the current user's queue.
        Returns information about the queue including currently playing track and next tracks.
        """
        try:
            results = self.sp.queue()
            return results
        except Exception as e:
            return f"Error getting queue: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves the queue but doesn't disclose behavioral traits such as whether it requires authentication, rate limits, or the format of the returned data. This leaves significant gaps in understanding how the tool behaves in practice.

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 a single, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and efficiently conveys the essential information, making it highly concise and well-structured.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the queue data includes (e.g., track order, metadata) or any prerequisites like authentication. For a tool that likely returns structured data, more context is needed to be fully helpful.

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 the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it correctly avoids mentioning any. A baseline of 4 is appropriate as it doesn't mislead or omit necessary parameter info.

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 ('current queue of tracks'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'get_current_track' or 'get_playback_state', which might provide overlapping queue-related information, so it falls short of a perfect score.

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. With siblings like 'get_current_track' and 'get_playback_state' that might include queue data, there's no indication of when this specific tool is preferred, leaving usage ambiguous.

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/ashwanth1109/mcp-spotify'

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