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 items to display podcast browse pages. Get normalized browsePage Pathfinder data with pagination limits and offsets.

Instructions

Retrieve Spotify Podcasts home. Returns normalized sections and items from Spotify's podcast home browsePage Pathfinder response.

Input Schema

TableJSON 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.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It only states the operation and source, without disclosing side effects, auth requirements, rate limits, or other behavioral traits. For a read operation, it's minimally acceptable but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: first for purpose, second for return details. No unnecessary information, front-loaded with the key action.

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

Completeness3/5

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

No output schema exists. The description mentions return format but not structure. With 6 optional parameters, the description lacks details on defaults or pagination behavior. Adequate but with gaps.

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 all 6 parameters. The description adds no further meaning beyond what the schema provides. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Retrieve'), the resource ('Spotify Podcasts home'), and the return type ('normalized sections and items'). It distinguishes this tool from siblings like spotify_home and other spotify_podcasts_* 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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for the podcast home page, but doesn't contrast with similar tools like spotify_home or spotify_podcasts_categories.

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