Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

discogs_search

Search Discogs for releases, masters, artists, or labels by query, with optional type filter and pagination to retrieve structured metadata like country, year, formats, genres, and labels.

Instructions

Search the Discogs database. Searches the Discogs database for releases, masters, artists and labels, optionally filtered to one type, with page and per_page (max 100). Release and master results carry country, year, formats, labels, genres, styles, catalog number and barcodes; artist and label results carry id, title and thumbnail.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
pageNo1-based page number, default 1
typeNoResult type filter
per_pageNoResults per page, default 50, max 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "release",
+  "master",
+  "artist",
+  "label"
+]
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavioral detail beyond the schema: the distinct result shapes per type (release/master carry country, year, formats, labels, genres, styles, catalog number, barcodes; artist/label carry only id, title, thumbnail) and the pagination cap of 100. It says nothing about authentication, rate limits, or result ordering, which is a gap for a no-annotation tool.

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?

Three sentences, front-loaded with the core action and followed by filters and result shape. Minor waste in the opening redundancy ('Search the Discogs database. Searches the Discogs database for...'), but otherwise efficient and information-dense.

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?

With no output schema, the description helpfully explains what each result type returns, and it covers the filter and pagination surface. Combined with the full-coverage input schema, an agent has enough to call it correctly; only auth/rate-limit context is absent.

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 q, page, type and per_page. The description restates the type filter and the per_page max without adding format, default, or syntax guidance beyond what the schema supplies. Baseline 3 applies.

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?

Specific verb ('Search') plus resource ('the Discogs database') and an explicit enumeration of what can be found: releases, masters, artists and labels. An agent immediately knows the scope, though the description never distinguishes this tool from siblings like discogs_release, discogs_master or discogs_artist.

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: it's a search entry point, and the `type` filter is framed as optional. There is no statement of when to prefer this over the sibling detail endpoints (discogs_release, discogs_artist, discogs_label_releases) that presumably consume its results, and no prerequisites or exclusions.

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