Skip to main content
Glama
Bandcamp MCP Server

Bandcamp MCP Server

bandcamp_guide

Explains how to handle Bandcamp tasks such as reading releases, checking sales and merch orders, updating stock, and managing download codes, with screens and sign-in link. Call it first.

Instructions

How to work in Bandcamp (read releases, sales and merch orders, update stock and manage download codes): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bandcamp_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Bandcamp, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden: it implies a read-only informational tool and references a sign-in link, hinting at authentication context, but never states whether it performs any navigation or mutation, or what form the answer takes. For a guidance tool that likely has no side effects this is tolerable, but the agent must guess.

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 compact sentence lists the covered workflows and ends with the key directive. The parenthetical is dense but each clause maps to a real capability; nothing is redundant, though the critical instruction would land harder if front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-output-schema primer, the description covers scope and invocation ordering adequately, but leaves open what the agent receives back (screens documentation, a sign-in URL, step lists) and whether authentication must be completed before other calls. A sentence on the return content would make it complete.

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?

There is a single optional 'task' parameter with 100% schema description coverage, so the schema already explains it. The description adds no syntax, examples, or hints about how task phrasing changes the returned guidance, so the 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?

The description names the resource (Bandcamp) and enumerates the covered workflows (reading releases, sales and merch orders, updating stock, managing download codes), which clearly distinguishes this primer from UI-action siblings like bandcamp_click or bandcamp_type. It stops just short of a crisp verb-first statement of what the tool returns.

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?

"Call this first" gives explicit ordering guidance relative to all sibling tools, which is exactly the routing an agent needs for a primer. It does not state any cases where this tool should be skipped or how it relates to individual steps after the first call.

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