Skip to main content
Glama

list_events_by_creator

Read-onlyIdempotent

List upcoming and ongoing Zindies events a creator (author/artist) is involved in, identified by the creator's public token. A creator relates to an event in two ways: as the host (events the creator itself hosts; relation "organized") or as a participant (a reserved booth, being listed as a participating creator, or hosting/speaking in one of the event's programs such as a workshop or talk). Use relation to choose which to include. Each event carries a relations array describing how this creator relates to it. Note that the organizer field is a different thing: it is the organizing body (a festival committee or group) that hosts some events, not this creator. Same response shape as list_events otherwise. Default range: today through 60 days ahead.

The response also carries calendar: a subscribable iCal feed of the creator's upcoming events (ics_url, webcal_url, google_calendar_url — same shape as list_events_by_place). Hand these to the user when they want to follow a creator's events in their calendar app.

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": {
      "creator_token": "<creator_token>"
    },
    "name": "list_events_by_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day of the range, inclusive (YYYY-MM-DD, e.g. "2026-12-31"). Default: `from` + 60 days. For one specific day pass the same date as `from`. A value earlier than `from` returns no events.
fromNoFirst day of the range, as an ISO 8601 calendar date in Japan time (YYYY-MM-DD, e.g. "2026-12-05"; no time or timezone part). Default: today. A multi-day event already under way on this day is included. A past date returns past events. An unparseable value falls back to the default.
kindNoReturn only events of this kind (non_genre = general ZINE event, zine_making = ZINE-making workshop, author = author event (talk, signing), festival_style = fair / market with many booths, zine_cafe = ZINE cafe, book_club = book club, utakai = tanka poetry gathering). Omit for every kind. Combined with `event_type` and the date range by AND.
limitNoMaximum number of events to return, soonest first. Default 20, max 50. There is no cursor: when `count` equals `limit` there may be more, so call again with `from` set to the start date of the last event returned.
localeNoResponse language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese. Pass the language the user is conversing in when it is one of these; otherwise omit it. Fields without a translation fall back to their source language (usually Japanese), so one response can mix languages. Tokens, ids, dates and URLs are the same in every locale. Default: ja.
relationNoWhich events to include: `organized` = events the creator itself hosts, `participating` = events they join through a reserved booth, a listing as participating creator, or a program (workshop / talk), `all` = both (default). An event matching both ways is returned once, with both values in its `relations`. Use `participating` for "where can I meet this creator?".all
event_typeNo`day` = single-day events (they have `started_at` / `ended_at`), `period` = multi-day exhibitions and fairs (`start_date` / `end_date`), `all` = both (default). Combined with the other filters by AND.all
creator_tokenYesPublic token of the creator: a short lowercase string such as "fqpi", the `token` field of a creator from search, get_creator, get_creation or get_event. Not the numeric `id` or the name. An unknown or non-public token returns an error result with `error: "not_found"` (a creator with no matching events returns `events: []`, not an error).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / creator_token / description
      Previous value: -"Public token of the creator."New value: +"Public token of the creator: a short lowercase string such as \"fqpi\", the `token` field of a creator from search, get_creator, get_creation or get_event. Not the numeric `id` or the name. An unknown or non-public token returns an error result with `error: \"not_found\"` (a creator with no matching events returns `events: []`, not an error)."
    • changedInput schema / properties / event_type / description
      Previous value: -"Restrict by event type."New value: +"`day` = single-day events (they have `started_at` / `ended_at`), `period` = multi-day exhibitions and fairs (`start_date` / `end_date`), `all` = both (default). Combined with the other filters by AND."
    • changedInput schema / properties / from / description
      Previous value: -"Range start (YYYY-MM-DD). Default: today."New value: +"First day of the range, as an ISO 8601 calendar date in Japan time (YYYY-MM-DD, e.g. \"2026-12-05\"; no time or timezone part). Default: today. A multi-day event already under way on this day is included. A past date returns past events. An unparseable value falls back to the default."
    • changedInput schema / properties / kind / description
      Previous value: -"Filter by event kind."New value: +"Return only events of this kind (non_genre = general ZINE event, zine_making = ZINE-making workshop, author = author event (talk, signing), festival_style = fair / market with many booths, zine_cafe = ZINE cafe, book_club = book club, utakai = tanka poetry gathering). Omit for every kind. Combined with `event_type` and the date range by AND."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of events to return. Default 20, max 50."New value: +"Maximum number of events to return, soonest first. Default 20, max 50. There is no cursor: when `count` equals `limit` there may be more, so call again with `from` set to the start date of the last event returned."
    • changedInput schema / properties / locale / description
      Previous value: -"Response language for translatable text fields (names, titles, descriptions). Pass the language the user is conversing in when it is one of the supported locales. Fields without a translation fall back to their source language. Default: ja."New value: +"Response language for translatable text fields (names, titles, descriptions): ja = Japanese, en = English, ko = Korean, zh-TW = Traditional Chinese. Pass the language the user is conversing in when it is one of these; otherwise omit it. Fields without a translation fall back to their source language (usually Japanese), so one response can mix languages. Tokens, ids, dates and URLs are the same in every locale. Default: ja."
    • changedInput schema / properties / relation / description
      Previous value: -"Which events to include: events the creator itself hosts (organized), events they join via booth/listing/program (participating), or both (all)."New value: +"Which events to include: `organized` = events the creator itself hosts, `participating` = events they join through a reserved booth, a listing as participating creator, or a program (workshop / talk), `all` = both (default). An event matching both ways is returned once, with both values in its `relations`. Use `participating` for \"where can I meet this creator?\"."
    • changedInput schema / properties / to / description
      Previous value: -"Range end (YYYY-MM-DD). Default: from + 60 days."New value: +"Last day of the range, inclusive (YYYY-MM-DD, e.g. \"2026-12-31\"). Default: `from` + 60 days. For one specific day pass the same date as `from`. A value earlier than `from` returns no events."
  2. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of events to return. Default 20, max 50."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), and the description adds real context beyond them: the default 60-day forward window, the per-event `relations` array, the `calendar` object with ics/webcal/google URLs and an instruction to hand those to the user, and a warning that `organizer` is not the creator. It does not discuss pagination limits, but the schema covers that.

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?

Purpose and scope are front-loaded in the first sentence, and the second paragraph is well separated for the calendar payload. There is some redundancy with the schema, particularly restating relation semantics, but each paragraph carries distinct 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?

With eight parameters, four enums, and no output schema, the description does the right work: it explains the response's `relations` and `calendar` fields and defers the rest to list_events. Full completeness would require describing the remaining top-level response fields rather than pointing at a sibling.

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 coverage is 100% with rich enum descriptions on `relation`, `kind`, `event_type`, and `locale`, so the schema already does the heavy lifting. The description adds only the conceptual note that an event matching both relations appears once with both values, which is a modest increment.

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?

Opens with a specific verb and resource ("List upcoming and ongoing Zindies events a creator is involved in") plus the identifier (creator's public token), and immediately disambiguates the two relation modes, which is exactly the axis that separates this tool from list_events or list_events_by_place.

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 routing guidance for the `relation` parameter ("Use `participating` for 'where can I meet this creator?'") and signals lineage with list_events by noting the identical response shape. It stops short of an explicit when-not/alternative statement such as 'for all events regardless of creator, use list_events', so it misses the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources