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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_appointment_note_delete

DestructiveIdempotent

Deletes a note from a GoHighLevel calendar appointment using the appointment ID and note ID.

Instructions

Delete Note Endpoint: DELETE /calendars/appointments/{appointmentId}/notes/{noteId} (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": {
      "appointmentId": "<appointmentId>",
      "noteId": "<noteId>"
    },
    "name": "ghl_calendar_appointment_note_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYesPath parameter (inferred from the URL template; the official spec omits its declaration).
appointmentIdYesAppointment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / appointmentId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
  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?

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful operational context — the required OAuth scope calendars/events.write and the v3 version header — but says nothing about whether the delete is hard or soft, whether it cascades, or what a successful response looks like.

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?

Three short, front-loaded lines with no filler: action, endpoint, and auth scope. The endpoint and auth metadata are valuable; only the 'Delete Note' header is redundant with the tool name.

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?

For a two-parameter destructive endpoint with full schema coverage and meaningful annotations, the description supplies the endpoint, auth scope, and API version — enough to invoke correctly. The remaining gap, return/error behavior on deletion, is minor since no output schema exists and the annotations already flag destructiveness.

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% with only two path parameters, so the schema already documents both inputs. The description adds no meaning beyond the URL template (e.g., no format constraints or guidance on obtaining noteId), which is acceptable given the schema does the work.

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 title line 'Delete Note' restates the tool name, but the endpoint path DELETE /calendars/appointments/{appointmentId}/notes/{noteId} makes the specific resource and its nesting explicit, distinguishing it from sibling note tools like ghl_calendar_appointment_note_update and ghl_calendar_appointment_note_list. The verb+resource is unambiguous, though it relies on the endpoint line rather than prose to be so.

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 versus alternatives such as updating or listing appointment notes, and no mention of prerequisites beyond the scope string. The agent must infer all usage conditions from the name and endpoint.

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