Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_podcasts_show_recommendations

Fetch Spotify podcast recommendations for a show URI; get recommended shows and episodes with titles, publishers, images, and Spotify URLs.

Instructions

Retrieve Spotify podcast recommendations. Lists shows and episodes that Spotify recommends alongside a podcast show given by uri. Each recommendation has a type, title, publisher, description, images and Spotify URL, and meta.count gives the number returned. The response echoes the show uri it was requested for.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify show URI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses the return shape: type, title, publisher, description, images, Spotify URL, `meta.count`, and echoed `uri`. It does not cover auth, rate limits, or pagination beyond count, but it provides solid output transparency for a read-only retrieval 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 action and followed by return details. No filler, though the return-field enumeration would be unnecessary if an output schema existed.

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?

Low-complexity read tool with no output schema; the description supplies purpose, input, and return structure, including count. Pagination limits or auth needs are unstated, but the core call is adequately covered.

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% and the single `uri` parameter is already documented as "Spotify show URI"; the description adds no syntax or format detail beyond saying it is given by `uri` and echoed back. Baseline 3 applies.

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 (retrieve) and resource (Spotify podcast recommendations) and clarifies it lists shows and episodes recommended alongside a given show. It does not name siblings, but the recommendation scope is distinct enough to separate it from show-detail or episode-list tools.

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

Usage Guidelines3/5

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

The description implies usage by specifying recommendations are for a show given by `uri`, but it never states when to choose this over siblings like `spotify_podcasts_show` or `spotify_podcasts_show_episodes`, nor when not to use it. This is implied usage rather than explicit guidance.

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