Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

play_from_search

Search Spotify by name and immediately play the best matching track or episode. Works for songs and podcasts without needing a URI.

Instructions

Search Spotify by name and immediately play the best match. Works for songs and podcast episodes — no URI needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch text, e.g. a song title or podcast episode name
marketNoISO 3166-1 alpha-2 country code — affects availability/relinking of results; defaults to the account market
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
device_idNoTarget device ID; uses active device if omitted
search_typeNoWhat to search for: 'track' (song) or 'episode' (podcast episode)track
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
    • addedInput schema / properties / market
      Added value: +{
+  "description": "ISO 3166-1 alpha-2 country code — affects availability/relinking of results; defaults to the account market",
+  "pattern": "^[A-Za-z]{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/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 reveals a key autonomy: it automatically picks the 'best match' and plays immediately. It lacks detail on failure modes (no match found), device selection behavior, or whether playback state is changed, but the core behavior is clearly disclosed.

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?

Two sentences with no wasted words. The core action, supported media types, and key differentiator are all front-loaded. It is concise and well structured.

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

Completeness4/5

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

For a 6-parameter tool with no output schema and no annotations, the description is adequate but not complete. It explains the main behavior and the no-URI value proposition, but it omits important execution details such as what happens on no match, whether playback starts on the active device, and how 'best match' is determined.

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?

Schema coverage is 100%, so all six parameters are already well documented in the schema. The description adds semantic value by clarifying that the query resolves to a playback target ('no URI needed') and that both songs and episodes are supported, which goes beyond the schema's parameter-level descriptions.

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 states a specific action (search + immediately play), a clear resource (Spotify content by name), and covers songs and podcast episodes. The phrase 'no URI needed' distinguishes it from URI-based playback tools, but it does not explicitly differentiate from siblings like play_on, queue_next, or search_tracks.

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?

It implies when to use this tool: when you want to search and play without a URI. However, it does not explicitly state when not to use it, nor does it name alternative tools for playback or precise search, so the guidance is clear but not explicit.

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