Skip to main content
Glama
Sign In
spotify-mcp-server

spotify-mcp-server

by hightechif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_by_search

Searches Spotify for a track or playlist based on a query and starts playback.

Instructions

Play a track or playlist by searching for it first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "play_by_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNotrack
queryYes
access_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description must carry behavioral disclosure. It only states it plays after searching, omitting what happens with multiple results, error behavior if no results, or impact on current playback. The destructive nature is implied but not detailed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, but too brief; sacrifices necessary details for brevity. Not an example of efficient conciseness as it leaves significant gaps.

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

Completeness1/5

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

Given no output schema, no annotations, and minimal description, the tool definition is highly incomplete. An agent lacks information about response format, error handling, practical usage constraints (e.g., device requirement), and expected behavior.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to parameters. It mentions 'query' implicitly but doesn't explain defaults for 'type' or the optional 'access_token'. Agent gains no extra understanding beyond parameter names.

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 is to 'play' and the resource is 'track or playlist' via searching. It effectively distinguishes from sibling 'search_spotify' which only returns search results. However, it doesn't specify whether it plays the first result or presents choices.

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 on when to use versus alternatives like 'search_spotify' (which only searches) or other playback tools. No mention of prerequisites such as an active playback device.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools