Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bandcamp_release

Retrieve structured metadata for a Bandcamp album or track, including artist, release date, tags, price, tracklist, credits, and physical packages. Inspect release details without audio URLs.

Instructions

Get one Bandcamp album or track. Returns one Bandcamp album or track page: title, artist, label, release date, tags, about text, credits, digital price, tracklist with durations, physical packages with prices and, for a track, its parent album and ISRC. Audio stream and download URLs are never returned.

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": {
      "url": "<url>"
    },
    "name": "bandcamp_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAlbum or track URL on an artist subdomain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it does disclose key traits: this is a read-only single-item fetch, it specifies the exact return fields, and it proactively states that audio stream and download URLs are never returned, heading off a likely wrong expectation. It says nothing about error behavior, rate limits, or auth needs, which keeps it short of a 5.

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 in the first clause, then a dense but purposeful field inventory in the second sentence, closing with the negative constraint. The long enumeration earns its place because no output schema exists, though the list could be grouped more compactly.

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 and no annotations, the description takes on both jobs and largely succeeds: it fully describes the returned shape and flags the one thing users would wrongly expect (stream URLs). Missing only failure modes and whether album vs track input changes the retrieval path, which is a minor gap for a one-parameter read tool.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents the URL format and subdomain constraint. The description adds only indirect meaning by noting that track URLs yield parent-album and ISRC data, which hints both URL types are accepted but adds little the schema does not already say.

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?

"Get one Bandcamp album or track" gives a specific verb and resource, and the follow-up enumerates exactly what comes back (title, artist, label, tracklist, packages, ISRC). It does not explicitly distinguish itself from siblings like bandcamp_artist or bandcamp_search, so the boundary is implied rather than stated.

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?

The description implies usage (fetch a single release page given a URL) but never states when to choose this over bandcamp_artist for discography lookups or bandcamp_search for discovery. No prerequisites, no exclusions, no named alternatives.

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