Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_album_tracks

Fetch tracks from a Spotify album by URI or ID, with offset and limit pagination; returns track titles, URIs, images, and album details.

Instructions

Retrieve Spotify album tracks. Lists the tracks of a Spotify album, identified by uri (a Spotify URI or open.spotify.com URL) or id. offset defaults to 0 and limit runs 1 to 50, default 50. Each track has its title, URI, subtitle, image and URL. The album's name, artists and track total come back alongside. An invalid identifier returns 400.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify album ID
uriNoSpotify album URI or open.spotify.com album URL
limitNoTrack limit, clamped to 1-50
offsetNoTrack offset

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 well: it discloses the return shape (title, URI, subtitle, image, URL per track plus album name, artists, track total) and the failure mode ('An invalid identifier returns 400'). It does not cover auth or rate-limit behavior, but for a read endpoint the added context is substantial.

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 purpose, then identifier, then paging, then return contents, then error. Every sentence is functional; the only minor waste is the near-synonym opening pair 'Retrieve ... tracks' / 'Lists the tracks'.

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, but the description compensates by enumerating the returned fields and the album metadata returned alongside, and it documents the identifier alternatives, paging bounds and the 400 error. Complete enough for an agent to call it correctly; only auth/pagination-total details are absent.

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 earns more by stating defaults the schema omits ('offset defaults to 0', 'limit ... default 50') and by framing uri and id as alternative identifiers for the same album, which the schema does not make explicit.

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 and resource: 'Retrieve Spotify album tracks' / 'Lists the tracks of a Spotify album'. An agent knows exactly what it returns, though it never names the sibling it is not (e.g. spotify_album or spotify_tracks_search), so sibling differentiation is left implicit.

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 the purpose (fetch tracks for a known album), but there is no explicit when-to-use/when-not guidance nor any pointer to alternatives like spotify_album for metadata or spotify_tracks_search for discovery. Adequate but leaves selection to inference.

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