Skip to main content
Glama
Sign In
setlist-mcp

setlist-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

setlist_unmark_attended

Idempotent

Remove a show from your attended list on setlist.fm by setlist ID. Reverses marking attended; no-op if not currently attended.

Instructions

Remove a show from YOUR attended list on setlist.fm, by setlist ID (reverses setlist_mark_attended). Authenticated via your setlist.fm session — SETLIST_SESSION_COOKIE, or a signed-in browser tab via the fetchproxy bridge. Idempotent: a no-op if not currently attended. Reversible with setlist_mark_attended. Removes the attendance and verifies by re-reading the setlist page. Returns attended, changed and verified. verified: true means the page shows the requested state. If verified is false, the toggle could not be checked: attended holds the state the re-read saw, or null if the page was unreadable, and changed is false — check the show on setlist.fm before reporting success. Results include a setlist.fm url; when you present this data, cite it as a clickable source link to setlist.fm (their API terms require followable attribution — no nofollow). If a result has no url, link to https://www.setlist.fm instead.

Input Schema

NameRequiredDescriptionDefault
setlistIdYesSetlist ID to remove from your attended shows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.3
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to actually remove attendance; omit for a dry-run preview.",
-  "type": "boolean"
-}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv0.7.0

TDQS

A4.4/5.0
Behavior5/5

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

Far exceeds the annotation baseline: annotations only declare idempotentHint/destructiveHint/openWorldHint, while the description details the auth mechanism (SETLIST_SESSION_COOKIE or fetchproxy bridge), the no-op behavior, page re-read verification, and full semantics of the returned attended/changed/verified fields including the failure case. This is exactly the behavioral context an agent needs before calling a mutation.

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?

Front-loaded with the core action and the sibling it reverses, then layers on auth, idempotency, and return semantics. It is longer than typical but most sentences carry load-bearing information given the absence of an output schema; the attribution/url guidance is slightly tangential but tied to the tool's results.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates fully by naming the return fields (attended, changed, verified, url) and explaining the verified=true/false cases. Auth requirements, idempotency, and reversibility are all covered, so an agent can call and interpret this tool correctly.

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 there is a single parameter, so the schema already documents setlistId. The description only restates that it is the setlist ID to remove, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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 (Remove) and resource (a show from YOUR attended list on setlist.fm), scoped by setlist ID. It explicitly names the sibling it reverses (setlist_mark_attended), so an agent can distinguish it from the other attendance tools without opening a schema.

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?

Makes clear the condition that selects this tool: it reverses setlist_mark_attended and is idempotent (a no-op if not currently attended). It also documents the required auth path and the reversibility. It does not, however, state explicit exclusions or contrast against a broader set of alternatives beyond the single sibling.

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