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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_service_booking_update

Idempotent

Updates an existing service booking by modifying its status, schedule, services, staff, location, or timezone while optionally bypassing availability and notice checks.

Instructions

Update Service Booking Update an existing service booking Endpoint: PUT /calendars/services/bookings/{bookingId} (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": {
      "bookingId": "<bookingId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_service_booking_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
bookingIdYesUnique Service Booking ID
overrideAvailabilityNoIf true the time slot validation would be avoided for any booking creation/update (even the skipSchedulingNotice)
skipSchedulingNoticeNoIf set to true, the minimum scheduling notice and date range would be ignored

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / services / example
      Added value: +[
      +  {
      +    "id": "a3b4c5d6e7f8901234567890",
      +    "staffId": "8MkU36Wps2w5bRbuGtw3"
      +  }
      +]
    • addedInput schema / properties / body / properties / services / items / properties / addOns / example
      Added value: +[
      +  {
      +    "id": "6985f6dfacf123513228d384"
      +  }
      +]
    • addedInput schema / properties / body / properties / services / items / properties / addOns / items / title
      Added value: +"ServiceAddOnDTO"
    • addedInput schema / properties / body / properties / services / items / title
      Added value: +"CreateBookingServiceDTO"
    • changedInput schema / properties / body / properties / status / enum
      Previous value: -[
      -  "confirmed",
      -  "cancelled",
      -  "invalid",
      -  "new",
      -  "showed",
      -  "no_show"
      -]New value: +[
      +  "confirmed",
      +  "cancelled",
      +  "invalid",
      +  "new",
      +  "showed",
      +  "noshow"
      +]
    • addedInput schema / properties / body / title
      Added value: +"UpdateServiceBookingDTO"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, idempotent, non-destructive, open-world operation. The description adds useful context in the required OAuth scope and endpoint/version, but does not explain side effects, replacement semantics, or response behavior beyond what annotations and schema provide.

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 short and front-loaded with the action and endpoint. The first line and second line are somewhat redundant, but overall it is efficient and easy to scan.

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 nested-body mutation with availability override flags and no output schema, the description is minimally adequate. It supplies the endpoint and auth scope, while the schema covers most field-level detail, but it says nothing about expected response or update semantics.

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%, so the schema already documents all four parameters and nested body fields. The description adds no parameter-specific semantics beyond the endpoint path, so baseline 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 names a specific verb and resource: 'Update an existing service booking,' and provides the exact endpoint. It does not explicitly distinguish this from sibling booking or appointment update tools, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'existing service booking' implies this is for modifying a booking rather than creating one, but there is no explicit when-to-use guidance, no exclusions, and no comparison to relevant alternatives such as appointment_update or service_booking_create.

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