Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_section

Fetch items from a Spotify browse section by URI, returning each item's type, title, subtitle, images, and URL plus totalCount. Use offset and limit to page results.

Instructions

Retrieve Spotify browse section. Returns the items of one Spotify browse section for uri (default spotify:section:0JQ5IMCbQBLqNPkcmYxQPQ), with its title, subtitle and totalCount. Each item has a type, title, subtitle, images and Spotify URL. offset defaults to 0; limit runs 1 to 50 and defaults to 20.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify section URI
limitNoSection item limit, clamped to 1-50
offsetNoSection item 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 performs reasonably: it describes the return payload in detail (title, subtitle, totalCount, and per-item type/title/subtitle/images/URL). It omits auth requirements, rate limits, and read-only status, but the return-shape disclosure is unusually strong for a tool lacking an output schema.

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-loaded with the purpose, followed by return contents, then parameter defaults. Dense but each sentence contributes information; no filler or redundancy besides the limit-clamp detail already in the schema.

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?

For a 4-param read tool with no annotations and no output schema, the description supplies the return structure and parameter defaults an agent needs. Only auth/rate-limit context is absent, which is a minor gap for a public browse 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 100%, so the baseline is 3, but the description adds genuine value beyond the schema by stating default values (uri default section URI, offset default 0, limit default 20) that the schema does not document. The limit clamping is repeated from the schema, but the defaults are a real addition.

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 names a specific verb ('Retrieve') and resource ('Spotify browse section'), and clarifies it returns the items of one section. It's clear enough to distinguish from generic search tools, though it doesn't explicitly contrast itself with sibling browse tools like spotify_home or spotify_podcasts_home.

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 implied by providing the URI parameter and its default, but there is no explicit when-to-use guidance or mention of alternative tools for other Spotify browsing needs. The agent must infer that this retrieves a specific section rather than a homepage or search result.

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