TimeTree MCP Server

get_calendar_members

Read-only

List calendar members with their user IDs, names, and roles to identify event attendees; for members without accounts, use the virtual members lookup.

Instructions

List the people who share a calendar (members with TimeTree accounts) with their user IDs, names, and roles. Use user_id for event attendees. For members without an account, such as children or pets, use get_calendar_virtual_members.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)
`include_deactivated`	No	Include deactivated members (default: false)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`members`	Yes
`calendar_id`	Yes

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": "number"
+    },
+    "members": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "number"
+          },
+          "is_active": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "role": {
+            "enum": [
+              "owner",
+              "member"
+            ],
+            "type": "string"
+          },
+          "user_id": {
+            "description": "Use in event attendees",
+            "type": "number"
+          }
+        },
+        "required": [
+          "user_id",
+          "name",
+          "role",
+          "is_active"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "calendar_id",
+    "members",
+    "total"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.4.0Oct 3, 2026

changedInput schema / properties / calendar_id / description

Previous value: -"The calendar ID"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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a meaningful behavioral boundary beyond that: it only returns account-holding members and excludes virtual members, with an explicit redirect for the excluded case. It stops short of describing ordering, pagination, or the include_deactivated default behavior, hence not 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?

Two compact sentences, front-loaded with the purpose before the routing guidance. The 'with their user IDs, names, and roles' clause slightly overlaps what the output schema already provides, but it is short and gives the agent a fast read on result shape.

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?

Given an output schema exists and parameter coverage is complete, the description needs only to convey purpose, scope, and the sibling boundary, all of which it does. An agent has everything required to call this correctly.

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 both calendar_id and include_deactivated are fully documented in the schema. The description references user_id only in its role as a returned field, not as a parameter, and adds no syntax or format detail beyond the schema. 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 the people who share a calendar') plus the scope constraint (members with TimeTree accounts) and the return shape (user IDs, names, roles). It immediately distinguishes itself from get_calendar_virtual_members, so an agent can route correctly without opening either 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 explicit usage instructions: 'Use user_id for event attendees,' and names the alternative tool with the exact condition that selects it ('For members without an account, such as children or pets, use get_calendar_virtual_members'). This is a textbook when/when-not/alternative breakdown.

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