Skip to main content
Glama
Sign In
@nightsquawktech/gohighlevel-mcp-server

@nightsquawktech/gohighlevel-mcp-server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete GoHighLevel Appointment

ghl_delete_appointment
Destructive

Delete an appointment by providing its event ID. Requires explicit confirmation before execution.

Instructions

Delete a calendar event with DELETE /calendars/events/{id}. Requires confirm: true and owner approval before live execution.

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": {
      "event_id": "<event_id>",
      "confirm": "<confirm>"
    },
    "name": "ghl_delete_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesRequired for destructive tools. The API call is made only when confirm is explicitly true.
event_idYesCalendar event ID.
response_formatNoOutput format: markdown for human-readable summaries, json for structured output.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this tool as destructive (destructiveHint=true), and the description adds that a 'confirm' parameter must be true and that 'owner approval' is needed before execution. This provides additional behavioral context beyond annotations, though details on what happens after deletion (e.g., irreversible, soft delete) are omitted.

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

Conciseness5/5

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

The description is a single sentence that efficiently communicates the core action and key requirements. No extraneous words; the structure front-loads the verb and resource. Every part earns its place.

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

Completeness4/5

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

Given the tool's simplicity (3 parameters, no output schema, good annotations), the description covers the main functionality and a critical requirement (confirm). It lacks mention of the response_format parameter's impact on output, but overall it is mostly complete for a destructive tool with well-documented schema.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds that 'confirm' must be true, reinforcing the schema note. For event_id and response_format, no extra meaning is added. The value is marginal but positive.

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 clearly states 'Delete a calendar event' with the HTTP method and endpoint, making the action and resource unambiguous. However, it does not explicitly differentiate from sibling tools like ghl_update_appointment or other delete operations, but the name and context are sufficient.

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

Usage Guidelines3/5

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

The description mandates 'confirm: true' and mentions 'owner approval,' giving a precondition and dependency. It does not provide when-not-to-use scenarios or compare with alternatives like updating the appointment status instead of deleting. The guidance is adequate but lacks depth.

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