Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_podcasts_home

Fetch Spotify Podcasts home sections and their items, including titles, publishers, images, and Spotify URLs, with pagination for pages and sections.

Instructions

Retrieve Spotify Podcasts home. Returns the Spotify podcasts home page as sections of items, for uri (default spotify:genre:podcasts-web). Each section has a title and items with type, title, publisher, images and Spotify URL. page_limit and section_limit default to 10 and run 1 to 50; the offsets default to 0.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify page or genre URI
page_limitNoPage pagination limit, clamped to 1-50
page_offsetNoPage pagination offset
section_limitNoSection pagination limit, clamped to 1-50
section_offsetNoSection pagination 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.8/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 burden and does disclose the return shape (sections with title and items containing type, title, publisher, images, Spotify URL) plus pagination behavior and default/clamping ranges. It omits auth requirements and rate-limit behavior, but for a read-only retrieval tool the disclosure is solid.

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, purpose front-loaded, then output shape, then pagination semantics. Efficient and well-ordered, with only a small redundancy between 'Retrieve Spotify Podcasts home' and 'Returns the Spotify podcasts home page'.

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?

No output schema exists, so the description appropriately explains the return structure and relevant defaults/ranges. Parameters are fully covered by the schema and the description reinforces the key ones; only auth/rate context is missing, which is minor for a public read endpoint.

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 already 100%, so the baseline is 3; the description adds genuinely new information by giving the default `uri` value, the default limit of 10, the 1-50 operating range, and that offsets default to 0. This supplements the schema beyond its 'clamped to 1-50' phrasing.

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 uses a specific verb (Retrieve) and resource (Spotify Podcasts home) and goes on to describe the returned structure of sections and items. It is clearly distinguishable from search/list siblings, though it never explicitly contrasts itself with the nearby spotify_home or spotify_podcasts_categories 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?

Usage is only implied: it is the podcasts home page fetch, and the default `uri` of `spotify:genre:podcasts-web` hints at the intended scope. There is no statement of when to prefer this over spotify_home, spotify_podcasts_categories, or spotify_podcasts_charts, and no exclusions.

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