TimeTree MCP Server

get_events

Read-only

Find calendar events by start time range, keyword, or label, sorted by start time, to answer what is on your schedule.

Instructions

Find events in a calendar by start time range, keyword, or label, sorted by start time. Use this to answer "what is on my schedule"; use get_updated_events or get_recent_activity for "what changed". Reads every page of the calendar, then filters; limit applies after sorting. Memos are included unless include_memos is false (list_memos returns only memos). When start_before is set, recurring events are expanded into each occurrence in the range. Occurrences share the series uuid, so update_event changes the whole series; use update_event_occurrence or delete_event_occurrence with the occurrence start_at to change one.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Optional maximum number of events to return, counted after filtering and sorting.
`query`	No	Optional case-insensitive keyword matched against title, note, and location.
`label_id`	No	Optional label filter. 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
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)
`start_after`	No	Optional Unix timestamp in milliseconds. Only return events starting after this time. If user provides a date like "2026-02-01", convert it to Unix timestamp (e.g., 1769904000000).
`start_before`	No	Optional Unix timestamp in milliseconds. Only return events starting before this time.
`include_memos`	No	Whether to include memos (category=2). Defaults to true.
`expand_recurring`	No	When start_before is set, return each recurring occurrence in the range instead of only the series start. Defaults to true.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`events`	Yes
`calendar_id`	Yes
`total_fetched`	No
`truncation_note`	No
`truncated_series`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.7.0Oct 22, 2026

changedInput schema / properties / label_id / description

Previous value: -"Optional label ID (1-10) filter."New value: +"Optional label filter. 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"

changedInput schema / properties / limit / description

Previous value: -"Optional limit on number of events to return."New value: +"Optional maximum number of events to return, counted after filtering and sorting."

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"
+            ]
+          },
+          "end_at": {
+            "description": "ISO 8601 date-time (UTC)",
+            "type": "string"
+          },
+          "end_timezone": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "has_recurrence": {
+            "type": "boolean"
+          },
+          "is_recurring_occurrence": {
+            "description": "Present on expanded occurrences of a series",
+            "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"
+          },
+          "series_start_at": {
+            "description": "ISO 8601 date-time (UTC)",
+            "type": "string"
+          },
+          "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"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "total_fetched": {
+      "type": "number"
+    },
+    "truncated_series": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "truncation_note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "calendar_id",
+    "events",
+    "total"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedv0.4.0Oct 3, 2026

changedInput schema / properties / calendar_id / description

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

addedInput schema / properties / expand_recurring

Added value: +{
+  "description": "When start_before is set, return each recurring occurrence in the range instead of only the series start. Defaults to true.",
+  "type": "boolean"
+}

addedInput schema / properties / include_memos

Added value: +{
+  "description": "Whether to include memos (category=2). Defaults to true.",
+  "type": "boolean"
+}

addedInput schema / properties / label_id

Added value: +{
+  "description": "Optional label ID (1-10) filter.",
+  "type": "number"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Optional case-insensitive keyword matched against title, note, and location.",
+  "type": "string"
+}

addedInput schema / properties / start_before

Added value: +{
+  "description": "Optional Unix timestamp in milliseconds. Only return events starting before this time.",
+  "type": "number"
+}

First observedv0.3.0May 27, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover read-only and open-world safety; the description adds genuinely non-obvious behavior: it reads every page then filters, limit applies after sorting, memos are included by default, and recurring events expand when start_before is set. It also warns that occurrences share the series uuid, so update_event mutates the whole series and update_event_occurrence/delete_event_occurrence must be used for one occurrence.

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 purpose and the sibling routing, then layers behavioral notes efficiently. It is dense rather than padded, though the recurring/update-series warning is slightly beyond the immediate calling decision.

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?

With an output schema present, return values need not be explained. The description still covers pagination, filter/sort/limit order, default memo inclusion, and recurring expansion, which is everything an agent needs to call it correctly on a complex calendar.

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. The description earns a step above by clarifying ordering semantics (limit applied after filtering/sorting), the include_memos default, and the interaction between start_before and expand_recurring, though these largely echo the schema text.

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 ('Find events in a calendar') plus the filter dimensions (start time range, keyword, label) and sort order. It explicitly distinguishes itself from get_updated_events and get_recent_activity, so an agent can select it 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 Guidelines5/5

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

Gives the exact question this tool answers ("what is on my schedule") and routes the alternative cases to get_updated_events and get_recent_activity for "what changed". Also notes list_memos as the memos-only alternative, leaving no ambiguity about when to pick a sibling.

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