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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_appointment_create

Create a calendar appointment for a contact using calendar, location, contact, and start time details; schedule events, recurring appointments, or status updates in GoHighLevel.

Instructions

Create appointment Endpoint: POST /calendars/events/appointments (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_appointment_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / appointmentStatus / description
      Added value: +"Appointment status"
    • addedInput schema / properties / body / properties / rrule / example
      Added value: +"RRULE:FREQ=DAILY;INTERVAL=1;COUNT=5"
    • addedInput schema / properties / body / title
      Added value: +"AppointmentCreateSchema"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the required OAuth scope 'calendars/events.write' and endpoint, but it does not disclose side effects such as notification/automation behavior or slot-validation rules.

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?

The definition is short and front-loads the action before endpoint and auth metadata. The source-file reference is somewhat internal, but the description remains compact and easy to scan.

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 complex appointment-creation call with many nested optional fields and no output schema, the description provides the endpoint and auth scope but omits high-level caveats around recurrence, notifications, and availability validation. The rich input schema fills most of the gap, but the description itself is only minimally complete.

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 the extensive nested body schema already documents fields like rrule, toNotify, and ignoreFreeSlotValidation. The description adds no parameter-level meaning beyond that schema, which is the expected baseline when the schema does the heavy lifting.

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 states a clear verb and resource: 'Create appointment', reinforced by the POST endpoint. It is distinguishable from update/get/delete siblings by the create verb, though the description never explicitly routes the agent away from those alternatives.

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 this tool versus ghl_calendar_appointment_update or other calendar creation tools. No prerequisites, exclusions, or alternative-selection conditions are provided.

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