GoHighLevel MCP Server

create_appointment

Schedule a new appointment in GoHighLevel CRM for a specific contact, with title, start and end times, and optional location.

Instructions

Create an appointment

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": {
      "contact_id": "<contact_id>",
      "title": "<title>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "create_appointment"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	Appointment title
`end_time`	Yes	End time (ISO 8601)
`location`	No	Location
`contact_id`	Yes	Contact ID
`start_time`	Yes	Start time (ISO 8601)
`response_format`	No	Response format	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 14, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states the action ('Create'), implying a write operation, but lacks details on side effects, required permissions, or return behavior.

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 concise (one sentence) but under-specified. It adds minimal value beyond the tool name, failing to earn its place with useful detail.

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

Completeness2/5

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

Given the complexity (6 parameters, no output schema), the description is incomplete. It lacks information about output, return format, or post-creation behavior. Annotations are absent, so the description should compensate but does not.

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 coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema's parameter descriptions. It lists no additional context for parameters.

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 'Create an appointment' clearly states the action and resource. It distinguishes from sibling tools like list_appointments and get_appointment, though it doesn't differentiate from other create tools (e.g., create_contact) which operate on different resources.

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?

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives, such as creating an appointment vs. creating an opportunity. No prerequisites or conditions are mentioned.

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