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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_group_create

Creates a calendar group for a GoHighLevel location using a name, slug, description, and active status.

Instructions

Create Calendar Group Endpoint: POST /calendars/groups (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars/groups.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": {
      "body": "<body>"
    },
    "name": "ghl_calendar_group_create"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / description / description
      Added value: +"Group description"
    • addedInput schema / properties / body / properties / isActive / description
      Added value: +"Whether the group is active"
    • addedInput schema / properties / body / properties / locationId / description
      Added value: +"Location ID"
    • addedInput schema / properties / body / properties / name / description
      Added value: +"Group name"
    • addedInput schema / properties / body / properties / slug / description
      Added value: +"Group slug"
    • addedInput schema / properties / body / title
      Added value: +"GroupCreateDTO"
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already disclose that this is a non-read-only, non-destructive, open-world operation with idempotentHint=false. The description adds the required OAuth scope 'calendars/groups.write' and API version, which is meaningful behavioral context beyond the annotations, though it does not discuss duplicate-slug behavior or creation side effects.

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?

The description is compact and front-loaded with the core action and endpoint. The source-file reference is somewhat extraneous, but it does not impede understanding.

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 create tool with rich schema coverage, annotations covering safety, and no output schema, the description provides the essential endpoint and auth requirement. It is nearly complete, though it could mention slug uniqueness or related tools.

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 GroupCreateDTO documents name, slug, isActive, locationId, and description. The description adds no parameter-level semantics beyond the schema, so the baseline of 3 is appropriate.

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 and resource ('Create Calendar Group') and adds the exact endpoint POST /calendars/groups. It doesn't explicitly contrast with sibling tools like ghl_calendar_group_update or ghl_calendar_group_validate_slug, but the purpose is unambiguous.

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 tool versus alternatives, such as validating a slug first with ghl_calendar_group_validate_slug or updating with ghl_calendar_group_update. The endpoint and OAuth scope indicate how to call it, not when to choose it.

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