Crawlora MCP

spotify_podcasts_episode

Read-only

Returns normalized public episode metadata from Spotify's getEpisodeOrChapter Pathfinder response, with episode page, embed page, and anonymous oEmbed fallbacks when Pathfinder is unavailable. Provide either uri or id; defaults to a known public episode when omitted. Use spotify_episodes_search to search Spotify episodes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spotify_podcasts_episode"
  }
}

Input Schema

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; defaults to a known public episode.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already covering the safety profile, the description adds real value: it discloses the multi-source resolution strategy (Pathfinder primary, then episode page, embed page, and anonymous oEmbed fallbacks) and the default-episode behavior. No auth or rate-limit detail, but strong for a read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the primary action and scoping, then the parameter contract, then the sibling routing. Dense with internal terminology but no wasted sentences.

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?

An output schema exists, so return values need not be explained, and the description covers sourcing, parameter defaults, and sibling routing. Complete enough for an agent to invoke correctly; the only minor gap is no guidance on error/empty results when the episode is not found.

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 both parameters are already documented in the schema. The description reinforces the uri-or-id choice and the default behavior but adds little syntax or format detail beyond what the schema provides. Baseline 3 is appropriate.

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 (returns) and resource (normalized public episode metadata), and names the sibling (spotify_episodes_search) it is not. The reference to Spotify's internal 'getEpisodeOrChapter' Pathfinder response and its fallback chain is implementation jargon that slightly clouds the core purpose for an agent.

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

Usage Guidelines4/5

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

Explicitly tells the agent to supply either uri or id and that it defaults to a known public episode when omitted, and routes searching elsewhere via 'Use spotify_episodes_search to search Spotify episodes.' Context is clear, though it doesn't state when-not to use this versus sibling detail tools like spotify_podcasts_show.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?