Crawlora MCP

spotify_artist_albums

Read-only

Fetch a Spotify artist's paginated discography items from the anonymous Web Player, with order/type filters and limit/offset. Use spotify_artist for artist details, spotify_album for one album, or spotify_albums_search to discover albums.

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

Input Schema

Name	Required	Description
`id`	No	Spotify artist ID, used when uri is omitted.
`uri`	No	Spotify artist URI or open.spotify.com/artist/... URL.
`type`	No	Discography type. Allowed values: album, single, compilation, appears_on, all. Default album.
`limit`	No	Result limit, clamped to 1-50, default 50.
`order`	No	Sort order. Allowed values: date_desc, date_asc, name_asc, name_desc. Default date_desc.
`offset`	No	Result offset, default 0.

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.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context beyond that: the data comes from the anonymous Web Player, results are paginated, and order/type filters apply. It could say more about default result size or pagination limits, but it meaningfully enriches the behavioral picture.

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, front-loaded with what the tool does and followed by routing guidance. Every clause earns its place with no redundancy.

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?

With an output schema present, return values need not be explained. The description covers purpose, source, pagination, filters, and sibling alternatives, and annotations cover the safety profile, so an agent has everything needed 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 description coverage is 100%, so the schema already documents id, uri, type, limit, order, and offset with defaults and allowed values. The description's mention of 'order/type filters and limit/offset' largely restates what the schema provides, so the 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 Spotify artist's paginated discography items) with clear scope, and explicitly distinguishes itself from sibling tools by naming spotify_artist, spotify_album, and spotify_albums_search. An agent can identify this tool's niche without opening any schema.

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?

Routes the agent explicitly to three alternatives with their purposes ('spotify_artist for artist details, spotify_album for one album, spotify_albums_search to discover albums'), which is strong when-to-use guidance. It doesn't sharply delineate the boundary against spotify_albums_search (search vs. artist-scoped fetch), so it stops just short of a full when/when-not treatment.

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?