Skip to main content
Glama

Discogs

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

Full-text search across Discogs (releases, masters, artists, labels). Filter by type, title, artist, format (e.g., "Vinyl", "CD"), country, year, genre, style, label.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page
typeNorelease | master | artist | label
yearNoRelease year or year-range
genreNoGenre filter
labelNoLabel filter
queryYesFree-text query
styleNoStyle filter
titleNoTitle filter
artistNoArtist filter
formatNoe.g., "Vinyl", "CD", "Album"
countryNoCountry of release
per_pageNo1-100 (default 25)

Output Schema

NameRequiredDescriptionDefault
pageYesCurrent page number (1-based)
totalYesTotal number of matching items across all pages
resultsYesSearch result items
per_pageYesNumber of results per page
returnedYesNumber of results returned in this response
total_pagesYesTotal number of pages available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "The Beatles Abbey Road"
+  },
+  {
+    "format": "Vinyl",
+    "genre": "Rock",
+    "page": 1,
+    "per_page": 50,
+    "query": "Pink Floyd",
+    "type": "artist"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "page": {
+      "description": "Current page number (1-based)",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "per_page": {
+      "description": "Number of results per page",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "results": {
+      "description": "Search result items",
+      "items": {
+        "properties": {
+          "barcodes": {
+            "description": "Associated barcodes",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "catalog_number": {
+            "description": "Catalog number",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "country": {
+            "description": "Country of release",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "discogs_url": {
+            "description": "Full Discogs URL to item",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "formats": {
+            "description": "Release formats (e.g., Vinyl, CD)",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "genres": {
+            "description": "Genre tags",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "Discogs item ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "labels": {
+            "description": "Label names",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "master_id": {
+            "description": "Master release ID if applicable",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "styles": {
+            "description": "Style tags",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "thumbnail": {
+            "description": "Thumbnail image URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Title of the item",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Item type: release, master, artist, or label",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Release year",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "type",
+          "title",
+          "year",
+          "country",
+          "formats",
+          "labels",
+          "genres",
+          "styles",
+          "catalog_number",
+          "barcodes",
+          "master_id",
+          "discogs_url",
+          "thumbnail"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of results returned in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of matching items across all pages",
+      "type": "number"
+    },
+    "total_pages": {
+      "description": "Total number of pages available",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "total",
+    "page",
+    "total_pages",
+    "per_page",
+    "returned",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. Description adds that it searches multiple Discogs entity types and supports many filters, providing behavioral context beyond annotations without contradiction.

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?

Two sentences: first establishes purpose and scope, second enumerates filters. Every word earns its place; no redundancy.

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?

Given the presence of an output schema and comprehensive annotations, the description adequately covers what the tool does and its primary filters, leaving no critical gaps for an agent to misunderstand.

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 coverage is 100% with descriptions for all 12 parameters. Description lists many filters but adds no new meaning beyond what the schema already provides; examples are helpful but not essential.

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?

Clearly states 'Full-text search across Discogs (releases, masters, artists, labels)' with specific verb and resource, distinguishing it from sibling search tools like 'search_within' which target different scopes.

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?

Lists many filters indicating typical usage, but does not explicitly state when to use this tool versus alternatives like 'search_within' or 'deep_research'.

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

All Discogs toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources