Bandcamp MCP Server and API by Cotlet

Send fan message in Bandcamp

bandcamp_send_fan_message

Read-onlyIdempotent

Send fan message in the user's own Bandcamp account from ChatGPT, Claude or any AI agent. Returns how to do it in Bandcamp step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Bandcamp Cloud Browser. Bandcamp's official API: Bandcamp has an API, but only for labels and merchandise fulfillment partners, who get access by emailing Bandcamp (checked 11 Oct 2026).

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_send_fan_message"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

This is the standout section: the description defuses an otherwise confusing readOnlyHint=true on a tool named 'send' by saying it 'opens nothing by itself' and only returns step-by-step screens/buttons/fields. It also explains why a browser is required (Bandcamp's API is limited to labels and fulfillment partners). It stops short of covering what happens if the Cloud Browser session is unavailable or how failures surface.

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?

Purpose and the 'returns steps, opens nothing' caveat are front-loaded in the first sentence, which is the right order. The closing API paragraph with the 'checked 11 Oct 2026' provenance is slightly digressive but justifies the browser-based approach, so it earns most of its space.

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 zero-parameter, no-output-schema tool, the description covers everything needed: what it returns (step-by-step instructions), that it performs no side effects, and which tools carry out the action. Nothing required to invoke it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema's empty object. Baseline for a parameterless tool applies; no meaning is lost.

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 (send fan message) plus the owning account, and immediately clarifies a distinction that the sibling list alone couldn't convey: this tool returns instructions rather than performing the send. An agent can tell from sentence one both what it gets and what it does not get.

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?

Explicitly prescribes the follow-on step: take the returned steps and execute them with the cotlet_browser_* tools in the user's Bandcamp Cloud Browser, which correctly points at the sibling family. There is no explicit when-not condition or named alternative for a one-shot send, but the two-step workflow is unambiguous.

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

All Bandcamp MCP Server and API by Cotlet 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?