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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_resource_delete

DestructiveIdempotent

Delete a calendar resource by ID and resource type (equipments or rooms) from a sub-account. Use it to remove rooms or equipment from GoHighLevel calendars when they are no longer needed.

Instructions

Uses the currently-documented (non-deprecated) Calendar Resources version, 2021-04-15. The v3-tagged variant of this operation in the v3 spec is marked deprecated (Services V1) with identical request/response fields — do not use Version: v3 for resource endpoints. Delete Calendar Resource Delete calendar resource by ID (Services V1) Endpoint: DELETE /calendars/resources/{resourceType}/{id} (Version header: v3; source: v3/calendars-v3.json) Requires a Sub-Account (location) token. OAuth scopes: calendars/resources.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": {
      "resourceType": "<resourceType>",
      "id": "<id>"
    },
    "name": "ghl_calendar_resource_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCalendar Resource ID
resourceTypeYesCalendar Resource Type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / id / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
    • addedInput schema / properties / resourceType / example
      Added value: +"equipments"
  2. First observedv2.0.0

TDQS

B3.2/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 genuinely new operational context: it requires a Sub-Account (location) token and the OAuth scope calendars/resources.write, which the agent needs before calling.

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?

Roughly half the text is versioning boilerplate that repeats itself and is self-contradictory: it says to use the non-deprecated 2021-04-15 version and 'do not use Version: v3', yet the endpoint line states '(Version header: v3)'. The actual action is buried behind that noise.

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 two-parameter destructive delete, the essentials are present: target, auth scope, and annotation-declared safety traits. But the internal version contradiction could cause an agent to hesitate or pick the wrong variant, and nothing is said about the effect on existing bookings using that resource.

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% and both parameters carry descriptions plus an enum for resourceType, so the schema does the work. The description restates 'by ID' but adds no format, casing, or constraint detail beyond what the schema already provides.

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 states a specific verb+resource ('Delete Calendar Resource... by ID') and even gives the DELETE endpoint path, so the operation is unambiguous. However, the opening versioning preamble muddies the framing and never distinguishes this tool from sibling delete operations such as ghl_calendar_delete or ghl_calendar_group_delete.

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?

The only 'when' guidance concerns which spec version/variant to prefer ('do not use Version: v3'), which is spec-internal routing rather than task-level guidance. It never says when to delete a resource versus updating it, nor how it differs from the other calendar delete siblings.

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