Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bandcamp_artist

Retrieve a Bandcamp artist or label page to get its name, location, bio, image, and discography grid with album and track URLs.

Instructions

Get a Bandcamp artist or label page. Returns a Bandcamp artist or label page: name, location, bio, image and the discography grid of albums and tracks with their URLs. Pass an entry's url to bandcamp_release for full detail.

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": {
      "artist": "<artist>"
    },
    "name": "bandcamp_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistYesArtist subdomain or https://{subdomain}.bandcamp.com URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden; it does disclose the returned payload (name, location, bio, image, discography grid with URLs), which substitutes for the missing output schema. It says nothing about failure behavior for nonexistent subdomains, whether the discography grid is truncated, or any rate/access constraints.

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?

Three short sentences, front-loaded with the action and then the return shape and the handoff. The phrase 'Bandcamp artist or label page' is repeated in sentence two, a minor redundancy, but nothing else is wasted.

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 single-parameter, annotation-free tool with no output schema, the description covers both what goes in and roughly what comes back, plus the follow-up tool. The remaining gap is edge-case behavior such as invalid subdomains or pagination of the discography.

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% and already explains the accepted subdomain or full URL format, so the description adds no syntax detail. The only added meaning is the implication that a URL from a discography entry can be fed to bandcamp_release, which is a workflow hint rather than parameter semantics.

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?

States a specific verb and resource ('Get a Bandcamp artist or label page') and covers both entity types the tool handles. It explicitly contrasts with bandcamp_release, so an agent can distinguish the two without inspecting schemas.

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

Usage Guidelines4/5

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

Gives concrete next-step routing: pass an entry's url to bandcamp_release for full detail, which tells the agent exactly how this tool fits into a two-step workflow. It does not cover when to prefer this over bandcamp_search or the artist tools from other sources, so a full when/when-not treatment is absent.

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

Deploy Server

Other Tools