Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

discogs_artist_releases

List a Discogs artist's releases and masters by artist ID, with paging and details like format, label, year, and want counts.

Instructions

List a Discogs artist's releases. Returns the releases and masters credited to a Discogs artist, identified by the required id. Paged with page (default 1) and per_page (default 50, max 100). Each entry has its id, type (release or master), title, artist, role, format, label, year, thumbnail, and want and collection counts, alongside the total item count and page count.

Input Schema

NameRequiredDescriptionDefault
idYesDiscogs artist id
pageNo1-based page number, default 1
per_pageNoResults per page, default 50, max 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/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 so reasonably: it discloses this is a listing operation, the paging behavior and defaults, and exactly what fields each entry contains. It omits auth/rate-limit context, but for a public read listing this is solid disclosure beyond the schema.

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 purpose in the first sentence, then required id, then paging, then the field inventory. It is a bit long due to the enumerated return fields, but with no output schema that enumeration earns its place rather than padding.

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?

Given there is no output schema, the description fills the gap by enumerating entry fields and the total/page counts, and it covers the required id plus paging. Missing only a hint on how to obtain the artist id and whether results are filtered, which keeps it short of a 5.

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`, `page` and `per_page` including their defaults and max. The description restates the same defaults and the max of 100 with no added meaning, so 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 (List) and resource (a Discogs artist's releases), and pins it to the required `id`. The phrasing cleanly separates it from sibling discogs_label_releases (label-scoped) and discogs_artist (the artist entity itself).

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 rather than stated: the agent can infer it is for expanding an artist into their discography, but there is no explicit 'use this when…' or note that an artist id must first be obtained via discogs_artist/discogs_search. The description notes the id is required but doesn't route the agent to the tool that produces it.

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