Skip to main content
Glama
Sign In
mcp-spotify

mcp-spotify

by obrien-matthew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_tracks

Search for Spotify tracks using query filters for genre, year, artist. Returns track names, artists, albums, and IDs.

Instructions

Search for tracks on Spotify.

Supports Spotify query syntax for filtering:

  • genre: "genre:rock"

  • year: "year:2020" or "year:2018-2022"

  • artist: "artist:radiohead"

  • combined: "genre:indie year:2020-2024"

Returns track names, artists, albums, and IDs.

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": "search_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes a search operation (read-only) but does not disclose rate limits, authentication needs, or response size. The basic behavior is implied, but not fully transparent.

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 concise, front-loaded with purpose, and includes well-structured examples. Every sentence adds necessary information without redundancy.

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?

With an output schema present and simple search functionality, the description covers query syntax and return fields. It lacks pagination details but is generally complete for a search tool.

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?

The description adds value by explaining the query syntax, which is not detailed in the schema (0% coverage). However, it does not describe the 'limit' parameter's effect or constraints, leaving a gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search for tracks on Spotify.' This specific verb-resource pair distinguishes it from sibling tools like search_artists and 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the query syntax and gives examples, implying when to use it. It lacks explicit exclusions or alternative tool references, but in context with siblings, usage is clear.

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