Skip to main content
Glama

Save or post a show or party

save_event
Destructive

Save the artist's own show, release party or listening party, or change one (pass event_id). It is saved as a DRAFT that only the artist sees, with whatever is known (only kind is needed), unless you pass post: true. Posting puts it on Scene for artists on Audora (and on the public page when is_public) and needs a title, starts_at and a place: a city and a country, and/or an online link. Post only when the artist asked for it to go out. An event already posted stays posted, so its changes need the same. Inviting artists or Audora stays the artist's to do in Audora; an edit keeps what they chose. Artist connections only.

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": {
      "event": "<event>"
    },
    "name": "save_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
postNotrue puts it on Scene now (needs title, starts_at and a place). Leave out to save a draft.
eventYes
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
event_idNoTo change one; leave out to save a new one.
idempotency_keyNoSend the same key if you retry, and the change happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / event / properties / is_public / description
      Previous value: -"Show it on the artist's public page."New value: +"Show it on the artist's public page once posted. Defaults: on for a show, off for a party."
    • changedInput schema / properties / event / properties / time_zone / description
      Previous value: -"IANA zone where it happens, e.g. Europe/Stockholm."New value: +"IANA zone where it happens, e.g. Europe/Stockholm. Needed with starts_at."
    • changedInput schema / properties / event / required
      Previous value: -[
      -  "kind",
      -  "title",
      -  "starts_at",
      -  "time_zone",
      -  "is_public"
      -]New value: +[
      +  "kind"
      +]
    • changedInput schema / properties / event_id / description
      Previous value: -"To change one; leave out to post a new one."New value: +"To change one; leave out to save a new one."
    • addedInput schema / properties / post
      Added value: +{
      +  "description": "true puts it on Scene now (needs title, starts_at and a place). Leave out to save a draft.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructiveHint true and readOnlyHint false, but the description adds the substance the annotations cannot: the draft-vs-posted visibility model, who sees a posted event (Scene, public page when is_public), and that a posted event 'stays posted, so its changes need the same' — a non-obvious irreversibility warning. It also notes an edit preserves the artist's earlier choices for invites.

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?

Dense but well ordered: what it does, the draft default, the posting exception and its requirements, then the irreversibility caveat. Some sentences are packed with multiple clauses, but no sentence is filler.

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 destructive, nested-object mutation with no output schema, the description covers the essential decision points and failure risks. Minor gaps: it does not mention that posted events cannot be retracted here (cancel_event presumably handles that) or when to reuse idempotency_key on retries.

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?

Schema coverage is 80%, so the schema carries most parameter documentation; the description adds the conditional-requirement logic that the schema's nested object does not encode (only kind is required to save, but posting needs title, starts_at and a place, with city+country 'and/or' online link). Useful, but it does not explain idempotency_key usage or the artist/label parameter.

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?

The first sentence names the exact resource (the artist's own show, release party or listening party) and both operations (create vs. change via event_id), so an agent distinguishes it from siblings like cancel_event or add_post 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 Guidelines5/5

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

It states the default path (saved as a DRAFT visible only to the artist), the condition that changes it (post: true), the prerequisites for that path (title, starts_at and a place — city+country and/or online link), and an explicit exclusion: 'Post only when the artist asked for it to go out.' It also scopes out inviting artists/Audora, which belongs elsewhere.

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