Skip to content

create_calendar MCP tool schema omits teamMembers, blocking personal calendar type creation #23

Description

@keithpaolino

createCalendar() in src/tools/calendar-tools.ts builds its GHL API payload from params.teamMembers, and MCPCreateCalendarParams types this as teamMembers?: GHLTeamMember[] ({ userId, priority?, isPrimary? }) — the field exists in code and types.

However, the tool's declared inputSchema (same file, create_calendar definition) never exposes teamMembers as a parameter. There's no way for an MCP client to supply it.

Repro:

create_calendar({ calendarType: "personal", name: "Test" })

Fails with a generic API error. calendarType: "event" with identical other params succeeds.

Suspected cause: GHL's API likely requires personal calendars to have an assigned team member/owner. Without a way to pass teamMembers, that requirement can never be satisfied, so personal (and possibly round_robin/collective, which also assign users) fail via this tool even though they're valid enum values.

Suggested fix: add teamMembers (array of {userId, priority?, isPrimary?}) to the create_calendar tool's inputSchema.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions