Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_artist_albums

Retrieve Spotify artist albums and discography items by artist ID, URI, or URL, with filters for album type, order, and pagination.

Instructions

Retrieve Spotify artist albums. Returns artist discography items from Spotify Web Player private Pathfinder responses.

Input Schema

TableJSON 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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add one useful non-obvious detail: the data comes from 'Spotify Web Player private Pathfinder responses,' which signals a non-official, potentially unstable data source. However, it does not disclose auth requirements, rate limits, pagination behavior, or output format, so it is only partially transparent.

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?

The description is two sentences with no wasted words. The primary purpose is front-loaded, and the second sentence adds a meaningful source detail. Every sentence earns its place.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has six optional parameters, no annotations, and no output schema, so the description must carry more weight. It only vaguely says 'Returns artist discography items' without describing the return structure, pagination, or how the type/order/limit parameters affect results. This is insufficient for an agent to confidently predict the tool's behavior.

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 all six parameters. The description adds no parameter-specific meaning beyond the schema, and the phrase 'artist discography items' only loosely maps to the 'type' parameter. With full schema coverage, the baseline of 3 is appropriate.

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 clearly states a specific verb and resource: 'Retrieve Spotify artist albums.' It also adds that it returns 'artist discography items,' which clarifies the scope. However, it does not explicitly distinguish itself from sibling tools like spotify_artist or spotify_artist_playlists, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or sibling tools that might be more appropriate for related tasks such as retrieving artist playlists or related artists. The only implied guidance comes from the tool name itself.

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