Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

bandcamp_search

Search Bandcamp by text or type to find artists, labels, albums, and tracks, with relevance-ordered IDs, URLs, artwork, tags, genre, and cap-reached flags.

Instructions

Search Bandcamp. Runs Bandcamp's site search and returns artists and labels, albums and tracks in Bandcamp's relevance order, each with its id, name, url and artwork (albums and tracks also carry the artist, tracks the album), plus any tags and genre that match the text. Bandcamp returns at most 50 hits (25 for artists) and does not page, so may_have_more reports when the cap was reached; narrow the text or pick a type to see more. Fan accounts are never returned. Pass a result'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

NameRequiredDescriptionDefault
qYesText to search, 1 to 100 characters
typeNoKind of hit to return: all (default), artists (artists and labels), albums or tracks

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the 50-hit (25 for artists) cap, that Bandcamp does not paginate, that may_have_more signals a truncated result, relevance ordering, and that fan accounts are excluded. These are exactly the behaviors an agent needs to interpret results correctly.

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 purpose and then packed with genuinely useful constraints; no filler sentences. It is dense to the point of being a single long run-on block, which costs a little readability but not substance.

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?

For a two-parameter search with no output schema and no annotations, the description covers return shape, ordering, caps, and cross-tool handoff thoroughly. An agent could call it and interpret the response without further information.

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 coverage is 100%, so the baseline is 3; the description adds value by explaining the consequence of the type parameter (choosing a type reveals more hits when capped) and what 'artists' includes (artists and labels). The q parameter's 1–100 character bound is left to the schema.

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 ... runs Bandcamp's site search') and enumerates the entity types returned (artists, labels, albums, tracks) along with their fields. Siblings are named for the next step (bandcamp_release, bandcamp_artist, bandcamp_discover), so it is clearly distinguishable.

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

Usage Guidelines4/5

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

Gives actionable guidance: use the type filter or narrow the text when the hit cap is reached, and pass URLs/slugs to the appropriate sibling tools. It does not explicitly state when another search-style tool should be preferred over this one, but the follow-up routing and cap-based advice are concrete.

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