TimeTree MCP Server

get_updated_events

Read-only

Lists events and memos changed after a Unix timestamp so you can sync or review calendar updates since a specific time, including deletions.

Instructions

List events and memos changed after a point in time, with their current content. Deleted ones are included with deleted: true. Use this to sync or review changes since a time; use get_recent_activity to see who changed what, and get_events to look up a schedule. Recurring events are returned once, not expanded.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Optional limit on number of events to return.
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)
`updated_after`	Yes	Unix timestamp in milliseconds. Only return events updated after this time. If user provides a date like "2026-02-01", convert it to Unix timestamp (e.g., 1769904000000).

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes
`events`	Yes
`calendar_id`	Yes
`total_fetched`	No
`updated_after`	Yes	ISO 8601 date-time (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calendar_id": {
+      "type": "string"
+    },
+    "events": {
+      "items": {
+        "properties": {
+          "alerts": {
+            "type": "array"
+          },
+          "all_day": {
+            "type": "boolean"
+          },
+          "attendees": {
+            "items": {
+              "type": "number"
+            },
+            "type": "array"
+          },
+          "category": {
+            "description": "1 = event, 2 = memo",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "checklist": {
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "created_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "deleted": {
+            "type": "boolean"
+          },
+          "deleted_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "end_at": {
+            "description": "ISO 8601 date-time (UTC)",
+            "type": "string"
+          },
+          "end_timezone": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "has_recurrence": {
+            "type": "boolean"
+          },
+          "label_color": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "label_id": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "location": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "note": {
+            "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",
+          "deleted"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "total_fetched": {
+      "type": "number"
+    },
+    "updated_after": {
+      "description": "ISO 8601 date-time (UTC)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "calendar_id",
+    "updated_after",
+    "events",
+    "total"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.4.0Oct 3, 2026

changedInput schema / properties / calendar_id / description

Previous value: -"The calendar ID to fetch updated events from"New value: +"The calendar ID from list_calendars (numeric string; numbers are also accepted)"

First observedv0.3.0May 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses two non-obvious behaviors: soft-deleted records are still returned with `deleted: true`, and recurring events are collapsed to one record rather than expanded. That materially changes how an agent interprets results. It stops short of describing ordering or how `limit` interacts with a large sync window, so it is strong but not exhaustive.

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 tight sentences: what it returns, the edge-case behavior, then the routing guidance. No restatement of the name, no filler, and the core purpose is front-loaded.

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?

An output schema exists, so return shape need not be explained, and the description covers the two things an agent would otherwise get wrong: deleted records appearing in results and recurring events not being expanded. Combined with 100% schema coverage on the three parameters, nothing needed for a correct call is missing.

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%, including the timestamp conversion guidance for updated_after, so the schema already carries the parameter burden. The description adds only the conceptual framing of "after a point in time" and nothing about limit or calendar_id semantics. Baseline 3 applies.

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 ("List events and memos changed after a point in time") plus the return scope ("with their current content"). It is immediately distinguishable from get_events (schedule lookup) and get_recent_activity (who changed what), so an agent can pick it 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?

Explicitly names the use case ("sync or review changes since a time") and routes to two named alternatives with the conditions that select them: get_recent_activity for attribution, get_events for a schedule. That is when-to-use plus when-not-to-use in a single sentence.

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