Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

calendars_create_calendar

Create a new calendar in GoHighLevel with configurable booking rules, availability, and team assignment to manage appointments.

Instructions

Create Calendar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
slugNo
notesNo
formIdNo
groupIdNoGroup Id
pixelIdNo
isActiveNoShould the created calendar be active or draft
eventTypeNo
guestTypeNo
openHoursNoThis is only to set the standard availability. For custom availability, use the availabilities property
preBufferNoPre-Buffer is additional time that can be added before an appointment, allowing for extra time to get ready
recurringNo
alertEmailNo
eventColorNo
eventTitleNo
locationIdNoDefaults to GHL_LOCATION_ID when omitted.
slotBufferNoSlot-Buffer is additional time that can be added after an appointment, allowing for extra time to wrap up
widgetSlugNo
widgetTypeNoCalendar widget type. Choose "default" for "neo" and "classic" for "classic" layout.
autoConfirmNo
descriptionNo
teamMembersNoTeam members are required for calendars of type: Round Robin, Collective, Class, Service. Personal calendar must have exactly one team member.
calendarTypeNo
consentLabelNo
slotDurationNoThis controls the duration of the meeting
slotIntervalNoSlot interval reflects the amount of time the between booking slots that will be shown in the calendar.
notificationsNo🚨 Deprecated! Please use 'Calendar Notifications APIs' instead.
preBufferUnitNoUnit for pre-buffer.
stickyContactNo
availabilitiesNoThis is only to set the custom availability. For standard availability, use the openHours property
formSubmitTypeNo
lookBusyConfigNoLook Busy Configuration
slotBufferUnitNoUnit for slot buffer.
allowBookingForNoMinimum number of days/weeks/months for which to allow booking events
allowRescheduleNo
enableRecurringNoEnable recurring appointments for the calendars. Please note that only one member should be added in the calendar to enable this
appoinmentPerDayNoNumber of appointments that can be booked for a given day
availabilityTypeNoDetermines which availability type to consider: - **1**: Only custom availabilities will be used. - **0**: Only open hours will be used. - **null**: Both custom availabilities and open hours will be considered.
slotDurationUnitNoUnit for slot duration.
slotIntervalUnitNoUnit for slot interval.
allowBookingAfterNoMinimum scheduling notice for events
allowCancellationNo
appoinmentPerSlotNoMaximum bookings per slot (per user). Maximum seats per slot in case of Class Booking Calendar.
isLivePaymentModeNo
calendarCoverImageNo
allowBookingForUnitNoUnit for controlling the duration for which booking would be allowed for
allowBookingAfterUnitNoUnit for minimum scheduling notice
formSubmitRedirectURLNo
googleInvitationEmailsNo
locationConfigurationsNoMeeting location configuration for event calendar
formSubmitThanksMessageNo
shouldAssignContactToTeamMemberNo
shouldSendAlertEmailsToAssignedMemberNo
shouldSkipAssigningContactForExistingNo
Behavior1/5

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

The description gives no behavioral information beyond a generic create action. Annotations indicate readOnlyHint=false and destructiveHint=false, so the description does not contradict them, but it adds nothing about side effects, permissions, or consequences of a create operation. With annotations present, the bar is lower, but the description still contributes zero behavioral context.

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

Conciseness2/5

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

The description is extremely brief (two words), but this is under-specification rather than effective conciseness. It saves space but at the cost of omitting all essential information, so it fails the structural test.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create operation with 54 parameters, no output schema, and complex sibling relationships, the description is grossly inadequate. It provides no information about required fields, constraints, or what the call returns. This is completely incomplete for an agent to use effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention any parameters. While the schema covers 48% of parameters with descriptions, the description itself adds no meaning to any of the 54 parameters. The tool's complexity requires the description to compensate, but it doesn't, making parameter semantics completely unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Create Calendar'), so it clearly conveys the core action. However, it does not differentiate from sibling tools like calendars_create_calendar_group or calendars_create_calendar_resource, and it is essentially a restatement of the tool name. It is adequate but not distinguishing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no context about when it is appropriate, and no exclusions or notes about prerequisites. It is a bare statement of action with zero usage guidance.

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/AIWerk/mcp-server-ghl'

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