Bandcamp MCP Server and API by Cotlet

List sales in Bandcamp

bandcamp_list_sales

Read-onlyIdempotent

List sales 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_list_sales"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses non-obvious behavior: the tool performs no action itself, returns a step-by-step procedure with screens, buttons and fields, and requires the user's Bandcamp Cloud Browser for the actual work. It also rules out the official API as an alternative, which is real operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the key behavioral disclosure are front-loaded, which is good, but "from ChatGPT, Claude or any AI agent" is filler and the trailing API note with a parenthetical check date is tangential. A tighter version would keep the instruction-plus-browser-tools contract only.

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 zero-parameter, read-only guidance tool with no output schema, the description covers what it returns, what it does not do, and what tools to use next. It could say more about the shape of the returned steps (e.g., whether they cover all sales or are filtered), but the essentials are present.

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 schema takes no parameters at all, so there is nothing for the description to disambiguate. Baseline for a zero-parameter tool 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 gives a specific verb and resource ("List sales in the user's own Bandcamp account") and adds the crucial clarification that it returns step-by-step guidance rather than data. It does not, however, distinguish itself from siblings such as bandcamp_export_sales_report or bandcamp_list_merch_orders, so the agent must infer which one to pick.

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?

Usage context is implied rather than stated: the tool returns instructions and "opens nothing by itself," so the agent should follow up with cotlet_browser_* tools. The API note hints at why this tool exists, but there is no explicit when-to-use versus the other Bandcamp sales/order tools.

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?