Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

eventbrite_create_event

Creates an Eventbrite event tied to an organization, accepting name, UTC start/end times, timezone, currency, and optional venue.

Instructions

Create an event on Eventbrite under an organization.

Input Schema

NameRequiredDescriptionDefault
nameYesEvent name/title
api_keyNo
end_utcYesEnd time in UTC, e.g. 2026-07-01T21:00:00Z
currencyYesISO currency code, e.g. USD
timezoneYesIANA timezone, e.g. America/New_York
venue_idNo
start_utcYesStart time in UTC, e.g. 2026-07-01T19:00:00Z
organization_idYesEventbrite organization id that will own the event

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.11
    • addedInput schema / properties / currency / description
      Added value: +"ISO currency code, e.g. USD"
    • addedInput schema / properties / end_utc / description
      Added value: +"End time in UTC, e.g. 2026-07-01T21:00:00Z"
    • addedInput schema / properties / name / description
      Added value: +"Event name/title"
    • addedInput schema / properties / organization_id
      Added value: +{
+  "description": "Eventbrite organization id that will own the event",
+  "type": "string"
+}
    • removedInput schema / properties / organizer_id
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / start_utc / description
      Added value: +"Start time in UTC, e.g. 2026-07-01T19:00:00Z"
    • addedInput schema / properties / timezone / description
      Added value: +"IANA timezone, e.g. America/New_York"
    • addedInput schema / properties / venue_id
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "start_utc",
-  "end_utc",
-  "timezone"
-]New value: +[
+  "name",
+  "organization_id",
+  "start_utc",
+  "end_utc",
+  "timezone",
+  "currency"
+]
  2. Addedv0.1.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It conveys mutation and organization ownership, but omits authentication needs, side effects, event status, validation, and error behavior for a write operation.

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 single sentence is front-loaded and free of filler. It is concise, though extremely terse for an 8-parameter mutation tool.

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 create operation with no annotations, no output schema, and 8 parameters, the description is incomplete. It states the core action but omits required-field guidance, authentication, return behavior, and mutation details.

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 75%, leaving api_key and venue_id undocumented. The description adds no parameter meaning beyond the schema and does not compensate for those gaps.

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 description states a specific verb, resource, platform, and ownership scope: 'Create an event on Eventbrite under an organization.' An agent can distinguish this from eventbrite_get_event and eventbrite_search_events without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

It gives no guidance on when to use this tool versus alternatives, prerequisites, or conditions. Usage is only implied by the verb 'Create.'

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