Skip to main content
Glama

AddEvent MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Create event

addevent_create_event

WRITE: creates a new event on a calendar (the account's default calendar if calendar_id is omitted). Creates a public event landing page and share links; it does not e-mail anyone, though people subscribed to that calendar's feed will see the event on their next sync. Needs title and datetime_start. POST /events.

Input Schema

NameRequiredDescriptionDefault
colorNoColor 1-20 from the palette.
titleYesEvent title (single line).
locationNoAddress or URL (meeting link). Use either location or location_id, not both.
reminderNoMinutes before the start for a calendar-app reminder (0-10800).
timezoneNoIANA timezone for the start/end (default: the calendar's timezone), or 'floating'.
free_busyNoHow the event shows in an attendee's calendar.
calendar_idNoCalendar to add the event to (see addevent_list_calendars); default calendar if omitted.
custom_dataNoArbitrary key-value pairs to store on the object (snake_case keys), e.g. an external id.
descriptionNoPlain text or simple HTML (keep under ~500 characters for cross-browser links).
location_idNoId of a saved location (0 = none). Not together with location.
datetime_endNoEnd date-time (default: start + 1 hour). Same formats as the start.
rsvp_enabledNoRequire an RSVP before the event can be added to a calendar.
rsvp_form_idNoRSVP form id or 'default' (see addevent_list_rsvp_forms).
all_day_eventNoAll-day event: only the dates are used.
internal_nameNoInternal name, never shown publicly.
datetime_startYesStart date-time: YYYY-MM-DD, YYYY-MM-DD hh:mm or YYYY-MM-DD hh:mm:ss.
organizer_nameNoOrganizer name (needs organizer_email).
recurring_ruleNoiCalendar recurrence rule such as FREQ=WEEKLY;COUNT=10. The start must match the rule. Omit for a one-off event; on update an empty string makes the event stop repeating.
organizer_emailNoOrganizer e-mail (needs organizer_name).
landing_page_template_idNoEvent landing page template id or 'default' (see addevent_list_event_templates).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, but the description goes well beyond them: it discloses side effects (public event landing page and share links are created) and the notification model (no e-mail is sent, though feed subscribers see it on next sync). This is exactly the kind of consequence-level context a write tool needs.

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-loads the WRITE marker and core purpose, then behavior, then requirements and the HTTP method. It is dense but each clause carries information; slightly long sentences keep it from being maximally tight.

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 20-parameter mutation tool with no output schema, it covers the essentials: required fields, default target, and side effects. It does not mention the returned identifier/object shape, but with no output schema that omission is minor.

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 description coverage is 100%, so every parameter is already documented, setting the baseline at 3. The description adds only the calendar_id default behavior and the two required fields, both of which the schema already states, so it does not meaningfully exceed the structured data.

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?

States a specific verb and resource ('creates a new event on a calendar') and roots it in the sibling landscape implicitly by clarifying the calendar target versus the other create_* siblings (calendar, rsvp_attendee). An agent can distinguish it from addevent_update_event/addevent_get_event 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 Guidelines3/5

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

It clarifies the key selection detail (default calendar when calendar_id is omitted) and the required inputs, which hints at how to invoke it. However it never routes the agent away from alternatives (e.g. update_event for modifying, or which sub-create to pick), so usage is only implied rather than explicit.

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

All AddEvent MCP by usefulapi toolsInspect
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