Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bandcamp_release

Read-only

Get one Bandcamp album or track page by url (https://{artist}.bandcamp.com/album/{slug} or /track/{slug}, as returned by bandcamp_discover and bandcamp_artist). Returns 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
urlYesRequired. A Bandcamp album or track URL such as https://artist.bandcamp.com/album/slug or https://artist.bandcamp.com/track/slug, as returned by bandcamp_discover or bandcamp_artist.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: the payload contents and the explicit negative constraint that audio stream and download URLs are never returned, which prevents an agent from promising playable audio. It does not mention failure modes for malformed or non-Bandcamp URLs.

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?

One front-loaded paragraph that opens with the verb and resource before the URL details and return summary. The long enumeration of returned fields (tags, about text, credits, prices, tracklist...) is somewhat list-heavy and partly duplicates the output schema, but nothing is padded or repetitive.

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?

For a single-URL lookup with a declared output schema, the description covers input provenance, payload scope, and the important audio-URL exclusion. The only redundancy is the field enumeration that the output schema already supplies, so nothing an agent needs is actually 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 description coverage is 100% with a single required parameter, and the schema already documents the URL format in detail. The description restates the same URL template plus the provenance hint (which sibling returns such URLs), adding only marginal meaning over the structured field.

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 ("Get one Bandcamp album or track page by url") and enumerates the exact URL shapes accepted. It also names the sibling tools (bandcamp_discover, bandcamp_artist) that produce those URLs, so an agent can tell it apart from the listing/browse siblings without opening any schema.

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?

The phrase "as returned by bandcamp_discover and bandcamp_artist" implicitly defines the workflow: this tool is the detail step after a listing call. It does not state any explicit exclusion or fallback (e.g. what to do if you only have an artist name), so it stops short of a full when/when-not statement.

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

All Crawlora MCP 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