Skip to main content
Glama

discogs_lists

Read-only

Fetch a user's Discogs lists or retrieve one list by ID to browse list contents and metadata.

Instructions

discogs_lists covers the lists toolset (2 operations). Token is sent as Authorization: Discogs token= and never in the query string. Local stdio server for one user. Not a hosted service. Actions: get: GET /lists/{list_id}. Get one list by id. list: GET /users/{username}/lists. List a user's lists.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "discogs_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON object for writes, or {csv} for inventory uploads. Tokens are redacted in output.
queryNoOpenAPI query parameters, such as page or per_page.
actionYesDiscogs operation to call.
paramsNoOpenAPI path parameters, such as release_id or username.
include_image_urlsNoIf true, keep image URL strings (images, thumb, cover_image, avatar_url). URLs are never fetched. Default false drops those fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the description need not restate safety. It adds genuinely useful context instead: how the token is passed (Authorization header, never query string), that it is a local stdio server for a single user, and that it is not hosted. It does not cover rate limits or pagination behavior, which is why it does not score higher.

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?

The description is short and front-loaded, with the toolset scope first and the action list last. The sentences have no filler, but it wastes a little space: "Local stdio server for one user" and "Not a hosted service" partly repeat each other, and the auth sentence belongs with the deployment note.

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 5-parameter read-only tool with no output schema, the description covers routing (action enum), auth, and deployment model, and the schema fills in parameter detail. It leaves return-value shape and pagination unaddressed, but those gaps are minor given the schema coverage and the read-only annotations.

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 params, query, body, and include_image_urls fields are already documented. The description adds only the path-parameter names ({list_id}, {username}) from the endpoint templates; it gives no further meaning for query, body, or include_image_urls. A 3 is the baseline when the schema does the heavy lifting.

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?

The description names the specific resource set (the lists toolset, 2 operations) and enumerates each action with its verb and endpoint: get one list by id, list a user's lists. That is enough for an agent to separate it from discogs_collection, discogs_wantlist, and discogs_user without opening their schemas.

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 only implied through the action list: pick "get" when you have a list_id, pick "list" when you have a username. There is no explicit when-to-use or when-not-to-use guidance, and no statement about which sibling tool handles adjacent tasks such as a user's collection.

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