Retrieve public Spotify podcast episode metadata by URI, URL, or episode ID; omit both to fetch a known public episode.
Retrieve Spotify podcast episode details. Returns public episode metadata. Provide either uri or id; defaults to a known public episode when omitted.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Spotify episode ID. Used when uri is omitted | |
| uri | No | Spotify episode URI or open.spotify.com episode URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses useful traits: the operation is a retrieval, results are public metadata, and omitting both identifiers yields a known public episode. It omits auth requirements, rate limits, error behavior, and response shape, so gaps remain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences with no wasted words, and the core purpose is front-loaded before output and parameter details. Every sentence contributes: purpose, return type, and identifier/default behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple lookup with no output schema and no annotations, the description covers the core action, return type, and input defaults. However, it leaves the agent without guidance on authentication, error cases, or when this endpoint is preferable to sibling search/listing tools, so it is adequate but incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the id and uri fields are already documented. The description adds the either/or requirement and the default fallback when both are omitted, but does not add syntax or precedence details beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Retrieve') and resource ('Spotify podcast episode details') and clarifies the return is public episode metadata. It does not explicitly distinguish this from sibling lookup/search tools such as spotify_episodes_search or spotify_podcasts_show_episodes, so an agent gets a clear purpose but no routing help.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description only explains how to supply an identifier ('Provide either uri or id') and the fallback when both are omitted. It never says when to choose this tool over alternatives like episode search, show-episodes listing, or other Spotify detail endpoints, and gives no when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.