Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

bandcamp_discover

Read-only

Browse Bandcamp Discover. tags is a comma-separated list of up to 5 tag slugs that an album must all carry (genres from bandcamp_filters, subgenres from bandcamp_related_tags). format is all, vinyl, cd or cassette; sort is best_selling (default), new or random; time_facet is an id 0 to 7 from bandcamp_filters; geoname_id restricts to a GeoNames place such as 5368361 (Los Angeles). size is 1 to 100 (default 24); pass the returned next_cursor as cursor for the next page. Each album has artist, location, price, release date, track count, duration, cover art and physical formats. total is the number of matching albums.

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

Input Schema

NameRequiredDescriptionDefault
sizeNoOptional. Albums per page, 1 to 100. Defaults to 24.
sortNoOptional. best_selling (default), new or random.
tagsNoOptional. Comma-separated tag slugs, up to 5, that an album must all carry (for example ambient,drone). Genres come from bandcamp_filters; related tags from bandcamp_related_tags.
cursorNoOptional. The cursor returned by the previous page. Omit for the first page.
formatNoOptional. Physical format filter: all (default), vinyl, cd or cassette.
geoname_idNoOptional. GeoNames id of a place to restrict artists to (for example 5368361 for Los Angeles).
time_facetNoOptional. Time-window id 0 to 7 as listed by bandcamp_filters. Omit for all time.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds pagination mechanics (returned next_cursor, size defaults, total matching count), but most of the remaining content restates parameters and result fields that are already structured. No auth, rate-limit, or failure-mode context is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, which is good, but the rest is a dense semicolon chain that repeats schema parameter descriptions and lists result fields despite an output schema existing. Several clauses could be dropped without losing agent-relevant information.

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 7-parameter, zero-required browse tool with an output schema, the definition covers filtering, ordering, paging, and result shape, so an agent can call it correctly. The remaining gap is routing guidance versus the other bandcamp_* tools, which is a usage concern rather than a completeness one.

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 the baseline is 3. The description largely mirrors the schema (tags up to 5, format values, sort options, size range), adding only the AND-semantics framing and the next_cursor name, neither of which is substantial beyond what the schema already documents.

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?

"Browse Bandcamp Discover" gives a specific verb and resource, and the body clarifies that results are albums matching tag/format/sort/geo filters. It also names where tag slugs come from (bandcamp_filters, bandcamp_related_tags), which implicitly separates it from those feeders. It never states how it differs from bandcamp_release, so it falls short of full sibling differentiation.

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 implied through workflow hints: get slugs from bandcamp_filters, related tags from bandcamp_related_tags, and pass the returned next_cursor for the next page. There is no explicit statement of when to reach for this tool instead of bandcamp_release or bandcamp_artist, and no when-not guidance.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources