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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_notification_delete

DestructiveIdempotent

Deletes a calendar notification by calendar ID and notification ID, helping remove obsolete event alerts from GoHighLevel calendars.

Instructions

Delete Notification Delete notification Endpoint: DELETE /calendars/{calendarId}/notifications/{notificationId} (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": {
      "calendarId": "<calendarId>",
      "notificationId": "<notificationId>"
    },
    "name": "ghl_calendar_notification_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendarIdYesCalendar ID
notificationIdYesNotification ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / calendarId / description
      Added value: +"Calendar ID"
    • addedInput schema / properties / calendarId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
    • addedInput schema / properties / notificationId / description
      Added value: +"Notification ID"
    • addedInput schema / properties / notificationId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
  2. First observedv2.0.0

TDQS

A3.6/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 openWorldHint=true, so the safety profile is covered. The description adds the required OAuth scope calendars/events.write, which is genuine auth context the agent cannot infer from the schema. It stops short of saying the deletion is permanent or describing error behavior.

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 endpoint and scope metadata are useful and front-loaded, but 'Delete Notification' and 'Delete notification' are redundant restatements of the title, and the source-file annotation (v3/calendars-v3.json) is low-value noise for an agent.

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 delete with full schema coverage and annotations carrying the safety hints, the description supplies the endpoint, version header, and required scope. What is missing is only the post-deletion consequence (irreversibility, not-found behavior), which is a modest gap rather than a blocker.

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% with both parameters documented as 'Calendar ID' and 'Notification ID', so the baseline is 3. The description adds only the path placement of the two IDs, which is marginal beyond what the schema already conveys.

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?

States a specific verb (Delete) and resource (Notification) and pins it to DELETE /calendars/{calendarId}/notifications/{notificationId}, so the agent knows exactly which entity is removed. It does not explicitly contrast itself with notification_update or notification_get, but the resource noun plus the path makes the target unambiguous.

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?

Usage is only implied: it deletes a notification identified by calendar and notification IDs, and the OAuth scope hints at the permission required. There is no explicit guidance on when to prefer this over ghl_calendar_notification_update (e.g., to clear instead of remove) or what happens if the notification does not exist.

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