Connections

Create a public hosted event (a page with RSVPs)

connections_event_create

Destructive

Use this when the member asks to create, host, plan or set up a PUBLIC event that others attend ('host an event', 'set up a meetup', 'create an event page for X'). Creates ONE hosted event on Connections - its own public page with RSVPs and tickets - as a draft, in the workspace this connection is bound to; a draft is private until published. It does not put anything on the member's own calendar: for 'add it to my calendar', a meeting, an appointment or blocked-out time, use connections_calendar_add. Pass dry_run:true first to see exactly what would be created without creating anything, and show that to the member before writing for real. Every other setting - tickets, registration questions, capacity, approval, the cover, and later changes to any of these - goes through events_manage_hosted_events (create-event / update-event) with the event's id.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	The event's name, in the member's words.
`dry_run`	No	true = return exactly what would be created and create nothing. Default false.
`ends_at`	No	Optional end time: an ISO date/time string, or unix seconds.
`location`	No	Optional public location label: a city, venue name, or 'virtual'.
`starts_at`	No	Optional start time: an ISO date/time string, or unix seconds.
`description`	No	Optional description of the event, shown on its public page.
`guests_see_who_came`	No	After the event, checked-in guests see who else came (the 'Who did you meet?' recap). Default true; false turns it off, e.g. for a large event. Each guest can still hide themselves.
`guest_list_visibility`	No	Who sees the guest list before the event: public (names), count_only (just the number), hidden. Default hidden.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

addedInput schema / properties / guest_list_visibility

Added value: +{
+  "description": "Who sees the guest list before the event: public (names), count_only (just the number), hidden. Default hidden.",
+  "enum": [
+    "public",
+    "count_only",
+    "hidden"
+  ],
+  "type": "string"
+}

addedInput schema / properties / guests_see_who_came

Added value: +{
+  "description": "After the event, checked-in guests see who else came (the 'Who did you meet?' recap). Default true; false turns it off, e.g. for a large event. Each guest can still hide themselves.",
+  "type": "boolean"
+}

AddedSep 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (which only flag non-read-only, destructive, non-idempotent), the description discloses that the event is created as a private draft until published, that it has no side effect on the member's calendar, and prescribes a dry_run-first workflow. These are substantive behavioral facts an agent could not infer from the annotation set.

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 trigger condition and the core behavior, and every clause (draft state, calendar exclusion, dry_run, config routing) carries distinct information. It is dense and slightly long, but no sentence is wasted.

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?

For a mutation tool with no output schema, the description covers what gets created, its draft/privacy state, the alternative tool for scheduling, the dry_run safeguard, and where downstream edits live. Nothing needed to invoke it correctly is missing.

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 100%, so the baseline is 3, but the description adds real value for dry_run by instructing the agent to run it first and surface the result to the member before writing. It does not add syntax detail for the other seven params, which the schema already covers.

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 and resource ('Creates ONE hosted event... its own public page with RSVPs and tickets') and immediately differentiates from the calendar sibling. An agent can distinguish this from connections_calendar_add and connections_events_list without opening any 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 gives explicit trigger phrasing ('host an event', 'set up a meetup'), an explicit exclusion ('for add it to my calendar, a meeting, an appointment or blocked-out time, use connections_calendar_add'), and routes all remaining configuration to events_manage_hosted_events. When-to-use, when-not, and the alternative are all named.

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

All Connections tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?