Skip to main content
Glama
Blackie360

Luma Events MCP Server

by Blackie360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Luma event

create_event

Create a Luma event after user confirms name, start time, and timezone. Configure visibility, registration, capacity, location, and more.

Instructions

Create a Luma event. Call only after the user has explicitly confirmed the event name, date/time, timezone, and supplied details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
slugNo
end_atNo
start_atYes
timezoneNoAfrica/Nairobi
confirmedYesMust be true only after explicit user confirmation.
visibilityNo
meeting_urlNo
max_capacityNo
description_mdNo
show_guest_listNo
waitlist_statusNo
geo_address_jsonNo
registration_openNo
location_visibilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.7.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / end_at / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
    • removedInput schema / properties / geo_address_json / additionalProperties
      Removed value: -false
    • changedInput schema / properties / max_capacity / anyOf
      Previous value: -[
-  {
-    "exclusiveMinimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / start_at / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-idempotent mutation, and the description's 'Create' wording is consistent. It adds the useful confirm-before-calling constraint, but does not disclose response behavior, side effects beyond creation, or whether the event is immediately published.

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?

The description is short and front-loaded: the action is stated first, followed by the important confirmation requirement. The first sentence is slightly redundant with the title, but the overall structure is efficient.

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

Completeness2/5

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

For a complex tool with 15 parameters, nested objects, and no output schema, this description is too sparse. An agent gets little guidance on optional fields, expected return value, or post-creation behavior, and the low schema coverage makes that gap more serious.

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

Parameters2/5

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

Schema description coverage is only 7%, so the description needed to compensate by explaining the many parameters. It mentions event name, date/time, timezone, and details, but leaves most of the 15 parameters—such as visibility, max_capacity, waitlist_status, and geo_address_json—unexplained.

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?

The description clearly identifies the action as creating a Luma event, using a specific verb and resource. It is naturally distinguishable from sibling tools like update_event and delete_event, though it does not explicitly contrast itself with them.

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?

The description gives a clear precondition: call only after the user has explicitly confirmed the event name, date/time, timezone, and details. It does not mention alternatives like update_event, but the confirmation gate is explicit and actionable.

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