Skip to main content
Glama
Sign In
Sonora MCP

Sonora MCP

by encodi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search Spotify

search
Read-onlyIdempotent

Find tracks, albums, artists, or playlists in the Spotify catalog by query and return their names, URIs, and links.

Instructions

Search the Spotify catalog for tracks, albums, artists or playlists. Returns names, URIs and links.

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

Input Schema

NameRequiredDescriptionDefault
typeNoAlias of `types` (same values), e.g. "artist". Do not pass both.
limitNoResults per type, 1-10 (Spotify caps search at 10 since Feb 2026).
queryYesFree-text search query.
typesNoWhat to search for: an ARRAY of "track" | "album" | "artist" | "playlist", e.g. ["artist"] or ["track","album"]. A single string such as "artist" is also accepted. Defaults to ["track"].
offsetNoIndex of the first result; use it to page through more results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0-dev

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is fully covered and the description only needs to add context. It does add the return shape ('names, URIs and links'), which is valuable given there is no output schema, but says nothing about the 10-result cap, per-type limits, or the type/types alias conflict that a caller must resolve.

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 short sentences, front-loaded with the verb and resource, followed immediately by what comes back. Nothing is wasted and nothing is buried.

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 simple read-only search with a fully described schema, the definition covers purpose and return values, which is the main gap left by the absent output schema. Paging behavior and the default type remain only in the schema, but that is a minor omission rather than a blocking one.

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?

Schema coverage is 100%, so all five parameters are documented in the schema, including the type/types alias warning, the 1-10 limit cap and the offset ceiling. The description adds no parameter meaning beyond that, 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?

States a specific verb (Search) and resource (the Spotify catalog) plus the four item kinds covered, so the agent knows exactly what this returns. It is clearly distinct from the siblings list_devices and now_playing, though the description never names them explicitly.

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?

There is no when-to-use or when-not-to-use guidance, no mention of how this relates to the sibling playback tools, and no advice on query construction or when to page with offset. The only context is the implied 'you want to find something in the catalog'.

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