Skip to main content
Glama
Bandcamp MCP Server

Bandcamp MCP Server

bandcamp_click

Clicks a numbered element on the current Bandcamp page by using the element number from the last read to navigate or interact with Bandcamp account pages.

Instructions

Click a numbered element on the current Bandcamp page.

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": {
      "element": "<element>"
    },
    "name": "bandcamp_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/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 discloses very little. It does not say whether clicking navigates away, mutates page state, may trigger downloads or form submissions, what happens on an invalid element number, or whether a re-read is required afterward — all critical for an interaction tool.

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?

A single short sentence with zero filler and the action front-loaded. It is efficient, though the brevity borders on under-specification rather than tight writing.

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

Completeness2/5

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

For an un-annotated, state-changing interaction tool with no output schema, the description should explain side effects, failure modes, and the read-then-click ordering. None of that is present, leaving the agent to guess what a click actually does to the page.

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?

Only one parameter exists and schema description coverage is 100%, with the schema itself stating "Element number from the last read," so the baseline is 3. The description's phrase "numbered element" merely echoes that without adding format, range, or staleness semantics.

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?

"Click a numbered element on the current Bandcamp page" names a specific verb (click) and a specific target (numbered element), which is enough for an agent to distinguish it from bandcamp_read or bandcamp_type. It does not explicitly contrast itself with those siblings, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use or when-not-to-use guidance and never mentions the prerequisite of running bandcamp_read first to obtain element numbers, nor when bandcamp_type is the better choice. The only hint at a workflow dependency lives in the parameter schema, not the description.

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