Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_artist_albums

Fetch a Spotify artist's albums, singles, compilations, or appearances by artist ID, URI, or URL. Filter by type and order, then paginate results with offset and limit.

Instructions

Retrieve Spotify artist albums. Returns an artist's Spotify discography by artist URI, open.spotify.com URL or id. Choose type (album, single, compilation, appears_on or all; default album) and order (default date_desc), and page with offset and limit (1-50, default 50). Each item has a type, title, subtitle, Spotify URI, external URL and images; total gives the full count.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify artist ID
uriNoSpotify artist URI or open.spotify.com artist URL
typeNoalbum, single, compilation, appears_on, or all
limitNoLimit, clamped to 1-50
orderNodate_desc, date_asc, name_asc, or name_desc
offsetNoOffset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / order / enum
      Added value: +[
+  "date_desc",
+  "date_asc",
+  "name_asc",
+  "name_desc"
+]
    • addedInput schema / properties / type / enum
      Added value: +[
+  "album",
+  "single",
+  "compilation",
+  "appears_on",
+  "all"
+]
  2. 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 a reasonable job: it discloses defaults (album, date_desc, 50), the 1-50 clamp, and the per-item and total return shape. It omits anything about rate limits or auth requirements, but the behavioral essentials for calling it are present.

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, then parameter usage, then return shape. Dense but each sentence adds something; the one weakness is that the parameter and return clauses run together in a single long paragraph, making it slightly harder to scan.

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 6-parameter, enumeration-heavy tool with no output schema, the description covers defaults, pagination, enum options, and item fields, so an agent has what it needs. Missing only marginal details such as auth/prerequisites, which keeps it short of the top score.

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 surfacing defaults (type=album, order=date_desc, limit=50) that the schema does not state, plus the enum semantics ('appears_on' vs 'all'). This meaningfully improves parameter selection.

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 states a specific verb and resource: 'Retrieve Spotify artist albums' and clarifies it 'Returns an artist's Spotify discography.' An agent can distinguish it from spotify_album (a single album) and spotify_albums_search (name search), though it never names those siblings explicitly, so differentiation is inferred 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?

Usage is implied through the input guidance (choose type/order, page with offset/limit), which is genuinely practical. However, there is no when-to-use vs. when-not guidance and no routing to alternatives like spotify_album, spotify_albums_search, or spotify_artist_playlists, so the agent must infer which tool is appropriate.

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