Bandsintown MCP Server and API by Cotlet

List upcoming events in Bandsintown

bandsintown_list_upcoming_events

Read-onlyIdempotent

List upcoming events in the user's own Bandsintown account from ChatGPT, Claude or any AI agent. Returns how to do it in Bandsintown step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Bandsintown Cloud Browser. Bandsintown's official API: Bandsintown has a public API, but it only reads: artist info and artist events (checked 11 Oct 2026).

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": "bandsintown_list_upcoming_events"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that the tool returns step-by-step instructions with screens, buttons, and fields, that it opens nothing by itself, and that it must be followed by browser actions. It also notes the official API's read-only limitation. These details help the agent understand the tool's actual behavior and side-effect profile.

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?

The description is reasonably short but the sentences are tangled: the first sentence implies listing events directly, then the next clause reverses that, and the final API note is only loosely connected. It could be front-loaded more clearly and tightened.

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 zero-parameter tool with no output schema, the description explains the return type (step-by-step instructions) and the follow-up workflow. However, it leaves out prerequisites such as whether a Bandsintown Cloud Browser session must already exist, and it does not clarify why an agent should choose this over sibling guide or browser tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters and schema description coverage is 100%, so the baseline is 4. The description does not need to explain parameters, and it does not introduce any parameter-related confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'List upcoming events in the user's own Bandsintown account', which suggests data retrieval, but then states it 'Returns how to do it in Bandsintown step by step' and 'opens nothing by itself'. The actual purpose is therefore a guide/instruction generator, not an event lister, leaving the agent with a confusing mismatch between the name and the described behavior.

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?

It tells the agent to use the result with cotlet_browser_* tools in the user's Bandsintown Cloud Browser, which is useful follow-up guidance. However, it does not say when to use this tool versus alternatives such as cotlet_app_guide or when the official Bandsintown API is sufficient, nor does it give any exclusion conditions.

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

All Bandsintown MCP Server and API by Cotlet tools Inspect

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

Need Help?