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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_block_slot_create

Create a blocked time slot on a GoHighLevel calendar to reserve time and prevent bookings during a specified start and end period.

Instructions

Create Block Slot Create block slot Endpoint: POST /calendars/events/block-slots (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": {
      "body": "<body>"
    },
    "name": "ghl_calendar_block_slot_create"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"BlockSlotCreateRequestDTO"
  2. First observedv2.0.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation profile is largely covered. The description adds real value by naming the required OAuth scope ('calendars/events.write') and endpoint/version, which the agent needs for auth planning. It says nothing about what the block slot does to existing availability or what is returned.

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?

Two of the four lines are redundant ('Create Block Slot' repeated as 'Create block slot'), which wastes the most valuable front-loaded space. The endpoint and scope lines do earn their place, but the opening is sloppy.

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 mutation tool with no output schema, the description carries the endpoint and auth scope and the schema fully documents the request body. Missing are the consequences of blocking a slot (does it override availability? is it reversible?) and any indication of the response, leaving a moderate gap for a non-idempotent write.

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 schema already documents every field, including the important 'Either calendarId or assignedUserId can be set, not both' exclusivity rule. The description contributes no parameter meaning at all, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 Block Slot') and names the HTTP endpoint, so the basic action is identifiable. However, the first two lines are a verbatim duplication of the tool name, and nothing distinguishes this from adjacent siblings like ghl_calendar_appointment_create or ghl_calendar_event_schedule_create, which also put events on a calendar. Purpose is inferable but not differentiated.

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 creating an appointment or event schedule, nor any stated precondition such as needing a calendarId or assignedUserId. The only mildly useful cue is the OAuth scope line, which implies a write permission requirement rather than a usage rule.

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