Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_episodes

Search for podcast episodes by query, filter by market, and control result count and offset.

Instructions

Search podcast episodes only (GET /search?type=episode). Quota: 🟢 single.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per type, 1–10. Default: 5
queryYesSearch query
marketNoISO 3166-1 alpha-2 country code, e.g. 'US'
offsetNoIndex of the first result to return, 0–1000
max_resultsNoMax items to return
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
include_externalNoPass "audio" to include externally-hosted audio items

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.28.0
    • changedInput schema / properties / market / description
      Previous value: -"ISO 3166-1 alpha-2 country code"New value: +"ISO 3166-1 alpha-2 country code, e.g. 'US'"
    • addedInput schema / properties / market / pattern
      Added value: +"^[A-Za-z]{2}$"
  2. Addedv1.26.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add useful behavioral context: it reveals the HTTP method (GET) and quota cost ('Quota: 🟢 single'). However, it does not disclose return format, pagination behavior, or other operational details beyond the schema.

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 compact clauses deliver the core scope and endpoint with zero filler. The essential 'episodes only' qualifier is front-loaded.

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

Completeness3/5

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

The schema covers parameters well, and the description provides endpoint and quota context. Yet with no output schema and no guidance on when to choose this over sibling search tools, the definition remains adequate but incomplete.

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%, so the schema already documents all seven parameters. The description adds no parameter-specific meaning, making the baseline 3 appropriate.

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 states a specific verb and resource: 'Search podcast episodes only', and reinforces it with the exact endpoint 'GET /search?type=episode'. This clearly distinguishes it from track/artist/album/show search siblings.

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 generic 'search' tool or other search_* siblings. The word 'only' implies scope but no explicit alternative or exclusion is given.

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