SpotifyMCP

find_tool

Read-onlyIdempotent

Search the live Spotify tool registry by name or description substring to identify the right tool for a job, especially when unsure which verb to use.

Instructions

Search the live tool registry by name or description substring — the fastest way to discover which of the 500+ tools handles a job. Discovery set: find_tool/inspect_tool/toolset_report are always available (also via catalog). Use this first when unsure which verb to use (e.g., playlist vs snapshot vs search).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max matches to return (default 25)
`query`	Yes	Case-insensitive substring to match against tool names and descriptions
`response_format`	No	'concise' (default) = prose bullet list; 'detailed' = the same prose; 'json' = the result payload as parseable JSON text, identical to structuredContent	concise

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.0.1Oct 1, 2026

changedInput schema / properties / response_format / description

Previous value: -"'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object"New value: +"'concise' (default) = prose bullet list; 'detailed' = the same prose; 'json' = the result payload as parseable JSON text, identical to structuredContent"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

Changed2 schema fields changedv1.31.0Sep 25, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedv1.28.0Sep 1, 2026

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

Addedv1.26.1Aug 29, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety and repeatability are covered by structured data. The description adds useful operational context — the registry is live, 500+ tools, and the discovery set is always available via catalog — but discloses nothing about result ordering, match behavior beyond 'case-insensitive substring', or limits. Adequate but not rich.

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, zero padding, with the core purpose front-loaded before the routing advice. The parenthetical about the discovery set is terse but earns its place by telling the agent these tools remain callable.

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

Completeness5/5

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

With annotations covering safety, an output schema covering return values, and full parameter documentation in the schema, the description only needed to supply purpose and routing — both delivered. Nothing an agent needs to invoke this correctly is missing.

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 description coverage is 100% with 3 parameters, each documented (query semantics, limit default/max, response_format enum meanings). The description adds no parameter guidance beyond the schema, so the baseline 3 is correct.

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?

States a specific verb (search) and resource (live tool registry) with the matching mechanism (name or description substring). It also quantifies scope (500+ tools), which lets an agent distinguish it immediately from the domain-specific search_* siblings that search Spotify content rather than the tool registry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says to use it first when unsure which verb applies, gives a concrete example of the ambiguity it resolves (playlist vs snapshot vs search), and names the sibling discovery tools (inspect_tool, toolset_report) plus the catalog as alternate access paths. Both the when and the alternatives are stated.

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

Deploy Server