Skip to main content
Glama
Bandcamp MCP Server

Bandcamp MCP Server

bandcamp_type

Enters text into a specified numbered field on the current Bandcamp page, enabling form completion and data entry for artist or label account workflows.

Instructions

Type text into a numbered field 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>",
      "text": "<text>"
    },
    "name": "bandcamp_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say whether typing triggers form submission, whether existing field content is replaced or appended, what happens with an out-of-range field number, or whether the page must be focused or opened first.

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 front-loaded sentence with no filler; the action and target come first. It is efficient but so terse that the brevity tips toward under-specification rather than maximum usefulness.

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 two-parameter interaction tool with no annotations and no output schema, the definition covers the basic mechanics but omits outcome information an agent needs to call it confidently, such as submit behavior and error conditions for invalid field numbers.

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?

Schema description coverage is 100%, so both parameters are already documented in the schema, giving a baseline of 3. The description slightly reinforces that 'element' refers to a field index on the current page but adds no syntax, format, or constraint details beyond that.

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 and resource: 'Type text into a numbered field' with the scope 'on the current Bandcamp page.' An agent can distinguish it from bandcamp_click and bandcamp_read without opening the schema, though it does not name those siblings explicitly.

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 is only implied: 'on the current Bandcamp page' signals it acts on already-loaded state and the numbered field references prior reading, but there is no explicit when-to-use, when-not-to-use, or prerequisite such as calling bandcamp_read first to obtain valid field numbers.

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