Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_track_similar_albums

Find albums similar to a Spotify track using its URI or ID, then limit results to 1–50 or request album-only recommendations.

Instructions

Retrieve Spotify track similar albums. Lists albums similar to a Spotify track, identified by uri or id. limit runs 1 to 50, default 50, and albums_only requests albums-only recommendations. Each album has its title, subtitle, publisher, images and Spotify URL. With neither uri nor id, a known public track is used.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify track ID. Used when uri is omitted
uriNoSpotify track URI or open.spotify.com track URL
limitNoAlbum limit, clamped to 1-50
albums_onlyNoRequest albums-only recommendations

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?

No annotations are provided, so the description carries the full burden and largely delivers: it discloses the fallback behavior when no identifier is given (a known public track is used) and enumerates the returned album fields. It does not discuss auth, rate limits, or pagination, but the fallback disclosure is genuinely valuable context.

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 and efficiently sized, with scoping and fallback surfaced early. The opening two sentences restate the same idea ('Retrieve ... similar albums' / 'Lists albums similar to ...'), a minor redundancy that keeps it just shy of full marks.

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-optional-param tool with no output schema, the description is complete enough: it covers identifiers, sizing, the albums_only flag, the no-input fallback, and the shape of returned albums. No annotation means the read-only nature is only implied, but nothing critical is missing.

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 baseline is 3, and the description adds value beyond the schema by stating the default limit value (50) which the schema only says is 'clamped to 1-50', and by clarifying what albums_only actually requests.

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: retrieving albums similar to a Spotify track, with the key input (uri/id) named. It is clearly distinct from the many news/sports siblings, though it never explicitly contrasts with the closely related spotify_track_recommended, so sibling differentiation is inferred from name rather than stated.

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 gives the identifier condition (uri vs id, and the fallback when neither is supplied), which is useful routing guidance. However it never states when to choose this over siblings like spotify_track_recommended or when a track-based similar-albums lookup is inappropriate.

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