Crawlora MCP

spotify_section

Read-only

Fetch a page of items from a known Spotify browse-section URI. Use spotify_home to discover the homepage sections first; this endpoint retrieves items from one selected section.

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_section"
  }
}

Input Schema

Name	Required	Description
`uri`	No	Spotify section URI, default spotify:section:0JQ5IMCbQBLqNPkcmYxQPQ.
`limit`	No	Section item limit, clamped to 1-50, default 20.
`offset`	No	Section item 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

A4/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 safety is covered. The description adds that this is a paged retrieval over a known URI and depends on prior discovery via spotify_home, but says nothing about auth, rate limits, or how pagination behaves.

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 tight sentences with the core action front-loaded and the workflow dependency second. No filler, nothing to trim.

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?

With an output schema present and full parameter coverage, the description needn't explain return values. It supplies the one thing structured data cannot: the two-step discover-then-fetch workflow with spotify_home. Minor gap in not noting URI sourcing edge cases.

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%, so uri, limit, offset, and the content-ratings flag are all documented in the schema. The description adds no syntax, format, or default information beyond what the schema already provides, so baseline 3 applies.

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?

States a specific verb (fetch) and resource (a page of items from a Spotify browse-section URI), and distinguishes itself from the sibling spotify_home by clarifying it operates on an already-discovered section URI rather than enumerating sections.

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

Usage Guidelines4/5

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

Explicitly names spotify_home as the prerequisite discovery step and frames this tool as the follow-up that pulls items from one selected section. Clear context, though it doesn't state exclusions (e.g., what happens if you have no URI).

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?