Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_podcasts_show

Fetch normalized metadata for any Spotify podcast show by URI, including content capability traits and episode content ratings, to power catalog and discovery apps.

Instructions

Retrieve Spotify podcast show metadata. Returns normalized podcast show metadata from Spotify Pathfinder.

Input Schema

TableJSON 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

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves metadata but does not disclose whether it's read-only, authentication needs, rate limits, or what 'normalized' means. Minimal behavioral context beyond the basic action.

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?

The description is concise with two sentences. The first sentence effectively states the action and resource. The second sentence is somewhat redundant but not overly verbose. Could be slightly improved by merging.

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

Completeness2/5

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

No output schema is present, and the description does not hint at the structure of the returned metadata (e.g., fields like title, description, episodes). For a tool with optional parameters and no output schema, more context is needed for an agent to understand the response.

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

Parameters2/5

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

Schema coverage is 100% with brief parameter descriptions, but the tool's description adds no value beyond those. It does not explain the purpose of the boolean parameters or provide examples. Parameter semantics are shallow.

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?

The description clearly states that the tool retrieves Spotify podcast show metadata from Spotify Pathfinder. It distinguishes from siblings like 'apple_podcasts_show' and 'spotify_podcasts_episode' by focusing on show-level for Spotify. However, it could be more specific about what metadata is included.

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 explicit guidance on when to use this tool vs alternatives like 'spotify_podcasts_search' or 'spotify_podcasts_show_episodes'. The description implies it's for a single show's metadata but does not provide when-not-to-use or mention alternative tools.

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