Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_podcasts_show

Retrieve Spotify podcast show metadata by URI, including name, publisher, description, total episodes, cover images, and URL. Optionally include content capability and episode rating fields.

Instructions

Retrieve Spotify podcast show metadata. Returns metadata for one Spotify podcast show by uri (default spotify:show:1QQJ7FElLE0K6CIfZNCxU4): name, publisher, description, media type, explicit flag, totalEpisodes, cover images and Spotify URL. The two include_ flags request extra content capability and content rating fields when Spotify supplies them.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify show URI
include_content_capability_traitNoInclude content capability trait
include_episode_content_ratings_v2NoInclude Spotify episode content ratings v2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose meaningful behavior: the default uri value (not in schema) and that the include_ flags add content capability/rating fields 'when Spotify supplies them', i.e. conditionally. However it omits auth requirements, rate limits, and error behavior, so it is only partially complete.

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, front-loaded with the purpose, then the return fields and flag behavior. There is mild redundancy between 'Retrieve Spotify podcast show metadata' and 'Returns metadata for one Spotify podcast show', but overall tight and free of padding.

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?

With no output schema, the description appropriately enumerates the returned fields (name, publisher, description, media type, explicit flag, totalEpisodes, cover images, URL) and explains the two optional flags. Only missing prerequisites/edge cases keep it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds beyond-schema value: it reveals the default uri (spotify:show:1QQJ7FElLE0K6CIfZNCxU4) and clarifies that the include_ flags pull conditional extra fields. This materially aids correct invocation.

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+resource ('Retrieve Spotify podcast show metadata') and scopes it to 'one Spotify podcast show by uri', which separates it from the list/search podcast siblings. It does not explicitly name an alternative like spotify_podcasts_show_episodes, so it falls short of a 5.

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 description explains how to call it (uri, default value) but gives no when-to-use guidance, no conditions, and no pointer to sibling tools such as spotify_podcasts_episodes_search or spotify_podcasts_show_episodes. Usage is only implied by the verb.

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