TimeTree MCP Server

create_event

Creates a TimeTree calendar event with title, start/end times, and optional details like attendees, reminders, recurrence, and checklist, returning the event with its UUID.

Instructions

Create an event in a TimeTree calendar and return it with its uuid. Other calendar members see it, and attendees may be notified. Supports all-day events, reminders, RRULE recurrence, attendees (user IDs from get_calendar_members), virtual member attendees, and a checklist. For a memo without a date use create_memo; to duplicate an existing event use copy_event.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Related URL
`note`	No	Event notes/description
`title`	Yes	Event title (required)
`alerts`	No	Notification offsets in minutes before the event, e.g. [5, 30]
`end_at`	Yes	Event end time as Unix timestamp in milliseconds. For all-day events, TimeTree uses an inclusive end date.
`all_day`	No	Whether this is an all-day event (default: false). TimeTree uses inclusive end dates for all-day events.
`category`	No	Event category (default: 1; memos use category=2)
`label_id`	No	Color label ID (1-10): 1=Emerald green, 2=Modern cyan, 3=Deep sky blue, 4=Pastel brown, 5=Midnight black, 6=Apple red, 7=French rose, 8=Coral pink, 9=Bright orange, 10=Soft violet
`location`	No	Event location
`start_at`	Yes	Event start time as Unix timestamp in milliseconds. For all-day events, use midnight of the start date.
`attendees`	No	Calendar user IDs attending this event
`checklist`	No	Checklist items to attach to the event
`file_uuids`	No	Attached file UUIDs if already uploaded
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)
`recurrences`	No	RRULE strings, e.g. ["RRULE:FREQ=DAILY;COUNT=2"]
`end_timezone`	No	End timezone (default: UTC)
`start_timezone`	No	Start timezone (default: UTC). Examples: "Asia/Seoul", "America/New_York"
`virtual_user_attendees`	No	Virtual member IDs/names attending this event

Output Schema

TableJSON Schema

Name	Required	Description	Default
`event`	Yes
`message`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Oct 22, 2026

changedInput schema / properties / label_id / description

Previous value: -"Color label ID (1-10). 1=Emerald, 2=Cyan, 3=Blue, 4=Brown, 5=Black, 6=Red, 7=Rose, 8=Pink, 9=Orange, 10=Violet"New value: +"Color label ID (1-10): 1=Emerald green, 2=Modern cyan, 3=Deep sky blue, 4=Pastel brown, 5=Midnight black, 6=Apple red, 7=French rose, 8=Coral pink, 9=Bright orange, 10=Soft violet"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "event": {
+      "properties": {
+        "alerts": {
+          "type": "array"
+        },
+        "all_day": {
+          "type": "boolean"
+        },
+        "attendees": {
+          "items": {
+            "type": "number"
+          },
+          "type": "array"
+        },
+        "calendar_id": {
+          "type": "number"
+        },
+        "category": {
+          "description": "1 = event, 2 = memo",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "checklist": {
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "created_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "end_at": {
+          "description": "ISO 8601 date-time (UTC)",
+          "type": "string"
+        },
+        "end_timezone": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "label_color": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "label_id": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "location": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "note": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "parent_id": {
+          "description": "Series uuid when this event is an edited occurrence",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "recurrences": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "start_at": {
+          "description": "ISO 8601 date-time (UTC)",
+          "type": "string"
+        },
+        "start_timezone": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "title": {
+          "type": "string"
+        },
+        "updated_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "uuid": {
+          "type": "string"
+        },
+        "virtual_user_attendees": {
+          "type": "array"
+        }
+      },
+      "required": [
+        "uuid",
+        "title",
+        "start_at",
+        "end_at",
+        "all_day"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "event"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.4.0Oct 3, 2026

changedInput schema / properties / calendar_id / description

Previous value: -"The calendar ID to create the event in (use list_calendars to get valid IDs)"New value: +"The calendar ID from list_calendars (numeric string; numbers are also accepted)"

changedInput schema / properties / calendar_id / type
```
Previous value: -"number"New value: +"string"
```

First observedv0.3.0May 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower, yet the description adds real side-effect context: other calendar members will see the event and attendees may be notified. It does not address the non-idempotent nature (repeated calls create duplicate events) or required permissions, which would have pushed this to a 5.

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 main action is front-loaded in the first sentence, followed by feature enumeration and then sibling routing. Three sentences, no filler; the only mild redundancy is re-listing features that the schema already exposes.

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 an 18-parameter mutation tool it is well covered: annotations supply the safety profile, an output schema exists (so return values needn't be explained, though the uuid is still mentioned), and schema coverage is complete. The remaining gap is that non-idempotency and permission requirements are left unstated.

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 one of the 18 parameters is documented in the schema and the baseline is 3. The description adds some meaning beyond it by explaining that attendees are user IDs sourced from get_calendar_members and by naming the virtual-member and RRULE features, but it doesn't clarify formats for timestamps, timezones, or label IDs.

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 ("Create an event in a TimeTree calendar") and adds the return artifact ("return it with its uuid"). It enumerates supported feature axes (all-day, reminders, RRULE, attendees, virtual members, checklist) and explicitly separates itself from create_memo and copy_event, so the agent can distinguish it from siblings 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 Guidelines4/5

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

It gives explicit routing rules with conditions: memos without a date go to create_memo, duplicating an existing event goes to copy_event. It also points at get_calendar_members as the source of attendee IDs. What's missing is guidance on when NOT to use it in favor of update_event/create_calendar, but the create-vs-update distinction is largely self-evident.

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