Crawlora MCP

bandcamp_search

Read-only

Search Bandcamp (q, 1 to 100 characters, for example radiohead or dub techno). type is all (default), artists (artists and labels), albums or tracks. Returns artist, label, album and track hits in relevance order, each with id, name, url and artwork (albums and tracks also carry the artist, tracks the album), plus tags and a genre that match the text. Bandcamp returns at most 50 hits (25 for artists) and does not page: may_have_more reports when the cap was reached. Fan accounts are never returned. Pass a hit's url to bandcamp_release or bandcamp_artist and a tag's slug to bandcamp_discover.

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": {
      "q": "<q>"
    },
    "name": "bandcamp_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Required. Text to search, 1 to 100 characters (for example radiohead or dub techno).
`type`	No	Optional. all (default), artists (artists and labels), albums or tracks.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds substantial operational detail beyond them: a hard cap of 50 hits (25 for artists), no pagination, a may_have_more flag signaling truncation, and the exclusion of fan accounts. These are exactly the behaviors an agent needs to interpret incomplete results; only return-format nuance is left thin (and an output schema covers that).

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 the action and scope, then return shape, then limits, then routing — a logical order with no filler. There is some duplication of the schema's q constraints and type values, but the density is justified for a search tool with a hard cap.

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 a 2-parameter tool with an output schema and annotations, the description covers everything the agent needs to call it and interpret results: what to search, how to filter, what comes back, the non-paging cap, and how to chain to detail tools. Nothing material is missing.

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%, so the schema already documents both q and type, including the 'artists (artists and labels)' nuance and the default. The description largely restates these values rather than adding new meaning such as matching semantics or quoting behavior, so the baseline 3 is appropriate.

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 ('Search Bandcamp') and immediately scopes what is searched: q length, the type filter values, and the object types returned (artist, label, album, track). It also carves out scope by noting fan accounts are never returned, letting an agent distinguish this from related Bandcamp lookup tools.

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?

Explicitly routes the agent: 'Pass a hit's url to bandcamp_release or bandcamp_artist and a tag's slug to bandcamp_discover.' This names the alternatives and the exact condition that selects each, so no inference is required.

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

All Crawlora MCP tools Inspect

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

Need Help?