Skip to main content
Glama
ehs208

TimeTree MCP Server

by ehs208

update_event

Update an existing TimeTree calendar event by providing only the fields to change. Modify title, time, location, attendees, recurrence, checklist, and more.

Instructions

Update an existing event in a TimeTree calendar. Only provide the fields you want to change. Requires CSRF token (automatically managed). Returns the updated event. Supports checklist, attendees, virtual attendees, alerts, RRULE recurrence strings, and category override.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendar_idYesThe calendar ID
event_uuidYesThe UUID of the event to update (from get_events)
titleNoNew event title
all_dayNoWhether this is an all-day event
start_atNoNew start time as Unix timestamp in milliseconds
start_timezoneNoNew start timezone (e.g., "Asia/Seoul")
end_atNoNew end time as Unix timestamp in milliseconds
end_timezoneNoNew end timezone
label_idNoNew color label ID (1-10)
categoryNoNew event category
noteNoNew event notes
locationNoNew event location
urlNoNew related URL
attendeesNoReplace calendar user attendee IDs
recurrencesNoReplace recurrence RRULE strings
alertsNoReplace notification offsets in minutes; use [] to clear
file_uuidsNoReplace attached file UUIDs
checklistNoReplace event checklist items. Use [] to clear checklist.
virtual_user_attendeesNoReplace virtual member attendees. Use [] to clear.
Behavior3/5

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

With no annotations, the description carries full burden. It discloses CSRF token management and that it returns the updated event. However, it omits side effects (e.g., notifications, recurrence handling) and error conditions, which are important for a mutation tool with 19 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no fluff: purpose, partial update hint, and a bullet list of supported features. Front-loaded and efficiently conveys essential information.

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?

Given 19 parameters, no output schema, and many siblings, the description covers key behavioral aspects (partial update, return value). It lacks details on error handling or specific parameter constraints, but the schema fills many gaps, making it reasonably complete.

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 each parameter is described. The description adds value by explaining partial update behavior ('Only provide the fields you want to change') and summarizing supported parameter groups (checklist, attendees, etc.), which aids in understanding which parameters are relevant.

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 clearly states 'Update an existing event in a TimeTree calendar', providing a specific verb and resource. Among siblings like create_event and delete_event, this tool is uniquely identified for event updates, and the partial update hint distinguishes it further.

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 clear usage context: 'Only provide the fields you want to change' implies partial update semantics. It lists supported features (checklist, attendees, etc.), helping agents decide when to use this tool. However, it does not explicitly contrast with create_event or mention prerequisites like event existence.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ehs208/TimeTree-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server