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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_resource_create

Create a GoHighLevel calendar resource for rooms or equipment with capacity, quantity, out-of-service count, and mapped service calendar IDs.

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. Create Calendar Resource Create calendar resource by resource type (Services V1) Endpoint: POST /calendars/resources/{resourceType} (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>",
      "body": "<body>"
    },
    "name": "ghl_calendar_resource_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
resourceTypeYesCalendar Resource Type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / calendarIds / example
      Added value: +[
      +  "Jsj0xnlDDjw0SuvX1J13"
      +]
    • addedInput schema / properties / body / properties / capacity / example
      Added value: +20
    • addedInput schema / properties / body / properties / description / description
      Added value: +"Description of the calendar resource"
    • addedInput schema / properties / body / properties / description / example
      Added value: +"Main conference room projector"
    • addedInput schema / properties / body / properties / locationId / description
      Added value: +"Location ID"
    • addedInput schema / properties / body / properties / locationId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
    • addedInput schema / properties / body / properties / name / description
      Added value: +"Name of the calendar resource"
    • addedInput schema / properties / body / properties / name / example
      Added value: +"Projector"
    • addedInput schema / properties / body / properties / outOfService / example
      Added value: +1
    • addedInput schema / properties / body / properties / quantity / example
      Added value: +5
    • addedInput schema / properties / body / title
      Added value: +"CreateCalendarResourceDTO"
    • addedInput schema / properties / resourceType / example
      Added value: +"equipments"
  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 readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered. The description adds real value with auth scope and endpoint details, but the version guidance is self-contradictory — it says 'do not use Version: v3 for resource endpoints' and then labels the same endpoint '(Version header: v3; source: v3/calendars-v3.json)' — which is behavioral noise rather than clarity.

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?

The first half of the description is internal API-versioning meta-commentary that an agent cannot act on and that contradicts the later endpoint line. The actual purpose appears only in the second paragraph, so the definition is neither front-loaded nor free of statements that do not earn their place.

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?

No output schema exists, so the description ideally would indicate what creation returns (e.g., resource ID) — it does not. Auth, endpoint, and method are covered, and the rich body schema compensates for most field semantics, but the conflicting version instructions leave an agent uncertain about which API surface is being invoked.

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% and the nested body documents every field with examples, so the schema carries the burden. The description adds only the hint that resourceType selects the resource kind ('by resource type'), plus the endpoint path template showing resourceType is a path segment; that is marginal but not zero extra meaning.

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 and resource ('Create Calendar Resource') and clarifies that creation is parameterized by resource type, which maps directly onto the enum (equipments/rooms). Siblings are ghl_calendar_resource_get/update/delete/list, so the create action is unambiguous. Not a 5 because the opening two sentences are about API versioning rather than the tool's purpose, delaying the reader.

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?

Prerequisites are stated ('Requires a Sub-Account (location) token', 'OAuth scopes: calendars/resources.write'), which is useful context for calling it. However, there is no guidance on when to prefer ghl_calendar_resource_create over related flows (e.g., mapping resources to service calendars via ghl_calendar_service_*), and no exclusions or preconditions around duplicates or existing resources.

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