Skip to main content
Glama
Bandcamp MCP Server

Bandcamp MCP Server

bandcamp_read

Reads the current Bandcamp page and returns visible text, numbered buttons, links, and form fields, with an option to inspect only a specific element for page understanding and navigation.

Instructions

Read the current Bandcamp page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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 at all, the description carries the full behavioral burden. It discloses the shape of the returned content, which is genuinely useful, but says nothing about side effects (implied read-only, never stated), behavior on large pages, truncation, or what happens when no page is loaded.

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 short sentence, front-loaded with the verb and resource, and the colon list efficiently enumerates returned content. Nothing is wasted, though the sentence is arguably too lean for a tool that returns structured page state.

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 simple one-parameter read tool with no output schema and no annotations, the description covers the essentials of what comes back but omits how the 'numbered' elements map to inputs for bandcamp_click and what happens with very large pages.

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 parameter and schema coverage is 100%, with the schema itself explaining 'Read only inside this element.' The description adds no meaning beyond that, so the baseline 3 applies; it doesn't explain how element numbering relates to the values reported back.

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?

States a specific verb (read) and a specific resource (the current Bandcamp page) and enumerates what is returned: text, numbered buttons, links, fields. That is enough to separate it from siblings like bandcamp_click and bandcamp_type, though it never names an alternative explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no prerequisites stated. The phrase 'the current Bandcamp page' only weakly implies that bandcamp_open must have been called first, and nothing routes the agent between this and bandcamp_status or bandcamp_guide.

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