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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_event_delete

DestructiveIdempotent

Deletes a GoHighLevel calendar event by ID, covering both appointments and block slots. Use it to remove a scheduled event from a calendar.

Instructions

Deletes any calendar event by ID (appointment or block-slot). Use ghl_calendar_appointment_* or ghl_calendar_block_slot_* for type-specific create/get/update. Delete Event Delete event by ID Endpoint: DELETE /calendars/events/{eventId} (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": {
      "eventId": "<eventId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_event_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
eventIdYesEvent Id or Instance id. For recurring appointments send masterEventId to modify original series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"DeleteAppointmentSchema"
    • addedInput schema / properties / eventId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real context beyond that: the deletion applies uniformly to appointments and block-slots, and it discloses the required OAuth scope (calendars/events.write) plus the endpoint. It does not say what side effects occur (notifications, cascade to notes, return payload), so it falls short of a 5.

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 first sentence is well front-loaded and the alternative routing is useful, but 'Delete Event' and 'Delete event by ID' then restate the title and first sentence verbatim, and the endpoint/version/source line is boilerplate. Roughly half the text is redundant.

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 destructive mutation with no output schema, it covers the endpoint, scope, and cross-type behavior, which is a reasonable amount. It is still silent on post-delete effects and on why a body object is mandatory, leaving a gap for a tool that removes data.

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 eventId's meaning (event or instance id, masterEventId for series) is already documented. The description adds nothing about the oddly required empty 'body' object or how instance deletion behaves, so it sits at the baseline when the schema carries the load.

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

Purpose5/5

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

The first sentence gives a specific verb plus resource ('Deletes any calendar event by ID') and explicitly widens scope to both subtypes (appointment or block-slot). An agent can distinguish this from the appointment_* and block_slot_* siblings without opening a schema.

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

Usage Guidelines4/5

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

It names the alternatives and the condition that routes to them ('Use ghl_calendar_appointment_* or ghl_calendar_block_slot_* for type-specific create/get/update'), implying delete is the shared path for any event type. It stops short of explicit when-not guidance, such as cancelling versus deleting or recurring-instance caveats.

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