Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

spotify_track_similar_albums

Read-only

Fetch album recommendation items from Spotify's similar-albums-for-track response using track id or uri; limit caps results. Use spotify_track_recommended for track suggestions, spotify_album for one album, or spotify_artist_related for related artists.

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

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, default 50.
albumsOnlyNoRequest albums-only recommendations when true.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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, covering the safety profile for a read operation. The description adds modest context (it reads from the similar-albums-for-track response; limit caps results) but no permission, pagination, or result-count behavior beyond what the schema/output schema convey.

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 no filler, and the core operation is front-loaded before the sibling routing. Every clause (source, id/uri input, limit behavior, alternatives) earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need no description, annotations cover the read/open-world profile, and all four parameters are fully described in the schema. Combined with the sibling routing, an agent has everything required to call it correctly.

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 id, uri, limit, and albumsOnly are all documented in the schema itself. The description reinforces that id or uri supply the track and that limit caps results, but adds no syntax, format, or default detail beyond the schema — baseline 3 is correct here.

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 (album recommendations / similar albums for a track) and pins it to a named Spotify response, so it cannot be confused with general recommendation or album lookups. It also names the siblings it differs from, making the intended operation unambiguous.

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 routes the agent: spotify_track_recommended for track suggestions, spotify_album for one album, spotify_artist_related for related artists. This gives strong differentiation, though it states the alternatives' domains without an explicit 'use this instead when…' condition linking back to this tool.

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

All Crawlora MCP toolsInspect
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