Skip to main content
Glama

List My Discogs Collection

discogs_list_collection
Read-only

List and browse the copies in your Discogs collection by artist or title, check what you own, and see recent additions with format, folder, condition, and release ID.

Instructions

List the Copies in the Owner's own Discogs Collection: vinyl, CDs, any Format.

Use it for "what do I have", "do I have anything by X", "what did I add recently" or to browse one Collection folder. Newest first unless another sort is asked for, and paged. Each line carries the Release, its Format, the folder, the condition (Media and Sleeve grades) and the release_id, and marks Releases the Owner has several Copies of. The query matches artist and title text only. Do not use it to find Releases the Owner lacks (use discogs_search), and use discogs_match_collection to check a list of albums from another source.

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": "discogs_list_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of Copies, from 1.
sortNoOrder of the list: added (default, newest first), artist, title or year (oldest first).added
limitNoCopies per page.
queryNoOnly Copies whose artist or title contain every word of this text, ignoring case, e.g. 'astley'.
folder_idNoOnly this Collection folder; 0 (default) for every folder. discogs_collection_summary lists the folders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond readOnlyHint=true/openWorldHint=true, it discloses default ordering (newest first unless another sort is asked for), that results are paged, what each result line contains (Release, Format, folder, Media/Sleeve condition, release_id), and that duplicate copies are marked. It also constrains matching behavior to artist and title text only, which is real behavioral context an agent would otherwise have to guess.

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?

Front-loads the core statement, then a usage block, then exclusions. The middle sentence about line contents is dense but earns its place because no output schema exists. No filler or restatement of the tool name.

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 no output schema, the description compensates by describing the shape of each returned line, ordering, and pagination. Combined with full schema coverage and the safety annotations, an agent has everything needed to select and invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description still adds meaning: default sort is newest first, results are paged, query matching is text-only against artist and title (no other fields), and folder_id can be used to browse a single Collection folder with discogs_collection_summary named as the way to discover folders.

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 and resource ("List the Copies in the Owner's own Discogs Collection") and scopes it ("vinyl, CDs, any Format"). It is immediately distinguishable from discogs_search (Releases the Owner lacks) and discogs_match_collection (checking an external list).

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

Usage Guidelines5/5

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

Gives concrete example intents ("what do I have", "do I have anything by X", "what did I add recently", browse a folder) and explicit exclusions: do not use to find Releases the Owner lacks, use discogs_search; use discogs_match_collection to vet an external list. Both the when and the when-not are named with the correct alternative.

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