@striderlabs/mcp-spotify

search_tracks

Find songs on Spotify by title, artist, or year, and retrieve album, duration, and popularity details.

Instructions

Search for songs on Spotify. Returns track name, artists, album, duration, URI, and popularity.

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

Name	Required	Description	Default
`limit`	No	Number of results to return (1-50, default: 20)
`query`	Yes	Search query (e.g., 'Bohemian Rhapsody', 'artist:Queen', 'year:2020')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the operation and return fields, omitting authentication requirements, read-only status, pagination behavior, and any side effects. This is minimal disclosure beyond the action itself.

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 two short sentences, front-loaded with the core action and followed by a concise list of returned data. Every word contributes, with no redundancy or filler.

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 2-parameter search tool with no output schema, the description adequately states the operation and enumerates return fields, which helps compensate for the missing output schema. However, it omits authentication prerequisites and available query qualifiers (e.g., artist:, year:) that the schema only partially covers.

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 schema covers 100% of parameters with descriptions and an example for query plus a range for limit. The description adds no parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 ('Search for songs on Spotify') and enumerates the returned fields. It identifies a distinct resource from sibling tools, but does not explicitly contrast with search_artists/search_albums/search_playlists, so differentiation is implicit.

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 is provided about when to use this tool versus the sibling search tools (e.g., search_artists, search_albums, search_playlists), nor any mention of when not to use it. The intended use case is only implied by the tool name and the schema's example query.

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