Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_podcasts_show_episodes

Retrieve Spotify podcast episodes by show URI, with offset and limit, to return names, descriptions, release dates, durations, playable status, URLs, images, and total episode count.

Instructions

Retrieve Spotify podcast show episodes. Returns the episodes of a Spotify podcast by show URI, with offset and limit (1-50). Each episode has its name, description, release date, duration in milliseconds, explicit and playable flags, Spotify URI, external URL and images; total gives the show's episode count.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify show URI
limitNoEpisode limit, clamped to 1-50
offsetNoEpisode offset
include_episode_content_ratings_v2NoInclude Spotify episode content ratings v2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does meaningful work: it discloses the operation is a retrieval, enumerates the returned episode fields (name, description, release date, duration in ms, explicit/playable flags, URI, external URL, images) and explains that `total` is the show's episode count. It still omits pagination edge behavior, auth requirements, and error cases, hence not a 5.

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?

Two sentences, zero filler, front-loaded with the purpose before the return-field inventory. The second sentence is a dense list but every element is informative for an agent that must consume the response.

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?

Without annotations or an output schema, the description compensates by describing return values and pagination inputs, which is the right coverage for a read-list tool. Gaps remain around the optional content-ratings parameter and pagination semantics, but nothing critical for a correct call is absent.

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 uri, limit, offset and the content-ratings flag. The description restates the 1-50 limit constraint but adds no syntax or format detail, and never mentions include_episode_content_ratings_v2 at all. Baseline 3 is correct.

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 and resource: retrieving episodes for a Spotify podcast show, keyed by show URI. It is distinguishable from spotify_podcasts_show (show metadata) in practice, but it does not name or contrast with any sibling such as spotify_episodes_search, so an agent must infer the boundary.

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?

The phrase 'by show URI' implies the prerequisite input, but there is no explicit when-to-use guidance, no when-not-to-use, and no mention of alternatives like spotify_episodes_search or apple_podcasts_show_episodes. The agent gets no routing help.

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