Skip to main content
Glama
Bandcamp MCP Server

Bandcamp MCP Server

bandcamp_open

Open a Bandcamp page in your signed-in Cloud Browser to manage releases, sales, merch orders, stock, and download codes.

Instructions

Open a Bandcamp page in your signed-in Cloud Browser (default https://bandcamp.com) to work with read releases, sales and merch orders, update stock and manage download codes.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://bandcamp.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose a meaningful trait: the browser session is authenticated, so the agent knows the page will be signed in. It does not say whether navigation replaces the current page, what happens on an invalid URL, or what the call returns (page content vs. just a success signal).

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 sentence that names the action, environment, and default first, then the use cases. No filler, though the trailing purpose list is slightly compressed into an awkward clause ('work with read releases').

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-required-parameter navigation tool with full schema coverage and no output schema, this is largely complete: it establishes the environment and default landing page. The main remaining gap is what the agent can expect after opening the page, which would help sequence it with bandcamp_read and bandcamp_click.

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?

The single url parameter is fully described in the schema, including its default, so the schema does the heavy lifting. The description repeats the same default and adds no format guidance (relative vs. absolute URLs, allowed hosts, non-Bandcamp targets), so it adds little beyond structured data.

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?

The description states a specific verb and resource ('Open a Bandcamp page') plus the execution environment ('signed-in Cloud Browser') and the default target URL. It is clearly distinguishable from siblings such as bandcamp_click, bandcamp_read, and bandcamp_close, which do not navigate to a page.

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 stated purposes (work with releases, sales and merch orders, update stock, manage download codes) imply when to reach for it, but there is no explicit guidance on when not to use it or which sibling to prefer for a given task. It gives enough context to make the tool plausible but leaves the choice between open/click/type/read to inference.

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