Crawlora MCP

spotify_podcasts_home

Read-only

Returns normalized sections and items from Spotify's podcast home browsePage Pathfinder response. pageLimit: Page pagination limit, clamped to 1-50, default 10. pageOffset: Page pagination offset, default 0. Use spotify_home to retrieve Spotify home sections.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spotify_podcasts_home"
  }
}

Input Schema

Name	Required	Description
`uri`	No	Spotify genre or page URI, e.g. spotify:genre:podcasts-web.
`pageLimit`	No	Page pagination limit, clamped to 1-50, default 10.
`pageOffset`	No	Page pagination offset, default 0.
`sectionLimit`	No	Section pagination limit, clamped to 1-50, default 10.
`sectionOffset`	No	Section pagination offset, default 0.
`includeEpisodeContentRatingsV2`	No	Include Spotify episode content ratings v2 when true.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that output is 'normalized' and mentions pagination clamping bounds, but discloses nothing about auth, rate limits, or how sections/items interleave. With annotations carrying the weight, a 3 is appropriate.

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?

Front-loads the purpose, then pagination details, then the alternative-tool hint. Reasonably efficient, though repeating param defaults already in the schema spends a sentence on little new value.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers scope, pagination, and the sibling alternative. Only the absence of explicit when-to-use guidance against close siblings keeps it short of complete.

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 baseline is 3. The description merely restates pageLimit and pageOffset values already fully documented in the schema and omits sectionLimit/sectionOffset/uri/includeEpisodeContentRatingsV2 entirely, adding no meaning beyond structured data.

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 ('Returns normalized sections and items from Spotify's podcast home browsePage') and implicitly distinguishes itself from spotify_home by scope. An agent can tell this is podcast-home browsing rather than generic home, though the differentiation relies on the reader inferring that 'podcast' narrows the target.

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?

It names spotify_home as the alternative for retrieving Spotify home sections, which is real routing guidance, but never states the condition that selects this tool over siblings like spotify_podcasts_categories or spotify_podcasts_charts. Usage is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?