Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_calendar_service_booking_create

Creates a new service booking in GoHighLevel calendars using contact, location, start/end time, timezone, and selected services.

Instructions

Create Service Booking Create a new service booking Endpoint: POST /calendars/services/bookings (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars/events.write

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "ghl_calendar_service_booking_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
overrideAvailabilityNoIf true the time slot validation would be avoided for any booking creation/update (even the skipSchedulingNotice)
skipSchedulingNoticeNoIf set to true, the minimum scheduling notice and date range would be ignored

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / services / example
      Added value: +[
      +  {
      +    "id": "a3b4c5d6e7f8901234567890",
      +    "staffId": "8MkU36Wps2w5bRbuGtw3"
      +  }
      +]
    • addedInput schema / properties / body / properties / services / items / properties / addOns / example
      Added value: +[
      +  {
      +    "id": "6985f6dfacf123513228d384"
      +  }
      +]
    • addedInput schema / properties / body / properties / services / items / properties / addOns / items / title
      Added value: +"ServiceAddOnDTO"
    • addedInput schema / properties / body / properties / services / items / title
      Added value: +"CreateBookingServiceDTO"
    • addedInput schema / properties / body / title
      Added value: +"CreatePublicServiceBookingDTO"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the write/safety profile is covered. The description adds genuinely useful non-annotation context: the required OAuth scope ('calendars/events.write') and the v3 API version header. It stops short of describing behavior such as default availability validation or what happens when a slot is taken.

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

Conciseness3/5

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

The heading 'Create Service Booking' immediately restates itself as 'Create a new service booking', wasting a line. The endpoint and OAuth lines are compact and useful, but nothing is front-loaded about when this tool is the right choice.

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

Completeness3/5

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

For a mutation tool with a deeply nested body and no output schema, the description plus annotations and full schema coverage are adequate for invocation. It omits key operational behavior an agent would want — that availability is validated by default unless overrideAvailability is set, and how conflicts or errors surface.

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 nested body, services, add-ons, and the overrideAvailability/skipSchedulingNotice flags, so the schema carries parameter meaning. The description contributes nothing parameter-specific beyond the version header, which is the expected baseline when schema coverage is complete.

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

Purpose4/5

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

The description gives a clear verb+resource ('Create a new service booking') and pins the exact endpoint (POST /calendars/services/bookings). It does not, however, distinguish this from closely related siblings such as ghl_calendar_appointment_create, ghl_calendar_event_schedule_create, or ghl_calendar_service_booking_update, so an agent must infer which creation path applies.

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?

There is no guidance on when to use service bookings rather than appointments or event schedules, and no prerequisites or exclusions are stated. The only contextual content is the endpoint and OAuth scope, which is metadata rather than usage direction.

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

Deploy Server

Other Tools