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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_service_update

Idempotent

Update a GoHighLevel calendar service by ID, including name, price, duration, staff, variations, buffers, and availability settings.

Instructions

Update Service Update service by ID. Endpoint: PUT /calendars/services/catalog/{serviceId} (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars.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": {
      "serviceId": "<serviceId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_service_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / payment / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "amount": {
      -        "description": "Service price",
      -        "example": 50,
      -        "type": "number"
      -      },
      -      "deposit": {
      -        "description": "Deposit amount or percentage value",
      -        "example": 20,
      -        "type": "number"
      -      },
      -      "depositType": {
      -        "description": "Deposit type",
      -        "enum": [
      -          "percentage",
      -          "amount"
      -        ],
      -        "example": "amount",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "amount": {
      +        "description": "Service price",
      +        "example": 50,
      +        "type": "number"
      +      },
      +      "deposit": {
      +        "description": "Deposit amount or percentage value",
      +        "example": 20,
      +        "type": "number"
      +      },
      +      "depositType": {
      +        "description": "Deposit type",
      +        "enum": [
      +          "percentage",
      +          "amount"
      +        ],
      +        "example": "amount",
      +        "type": "string"
      +      }
      +    },
      +    "title": "PaymentDTO",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / properties / payment / example
      Added value: +{
      +  "amount": 50,
      +  "deposit": 20,
      +  "depositType": "amount"
      +}
    • addedInput schema / properties / body / properties / staff / example
      Added value: +[
      +  {
      +    "id": "65e5f6dfacf123513228d384"
      +  }
      +]
    • addedInput schema / properties / body / properties / staff / items / title
      Added value: +"StaffDTO"
    • addedInput schema / properties / body / properties / variations / example
      Added value: +[
      +  {
      +    "id": "65e5f6dfacf123513228d385",
      +    "name": "Standard Haircut",
      +    "serviceDuration": 30
      +  }
      +]
    • changedInput schema / properties / body / properties / variations / items / properties / payment / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "amount": {
      -        "description": "Service price",
      -        "example": 50,
      -        "type": "number"
      -      },
      -      "deposit": {
      -        "description": "Deposit amount or percentage value",
      -        "example": 20,
      -        "type": "number"
      -      },
      -      "depositType": {
      -        "description": "Deposit type",
      -        "enum": [
      -          "percentage",
      -          "amount"
      -        ],
      -        "example": "amount",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "amount": {
      +        "description": "Service price",
      +        "example": 50,
      +        "type": "number"
      +      },
      +      "deposit": {
      +        "description": "Deposit amount or percentage value",
      +        "example": 20,
      +        "type": "number"
      +      },
      +      "depositType": {
      +        "description": "Deposit type",
      +        "enum": [
      +          "percentage",
      +          "amount"
      +        ],
      +        "example": "amount",
      +        "type": "string"
      +      }
      +    },
      +    "title": "PaymentDTO",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / properties / variations / items / properties / payment / example
      Added value: +{
      +  "amount": 50,
      +  "deposit": 20,
      +  "depositType": "amount"
      +}
    • addedInput schema / properties / body / properties / variations / items / title
      Added value: +"UpdateServiceVariationDTO"
    • addedInput schema / properties / body / title
      Added value: +"UpdateServiceDTO"
  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 readOnly=false, idempotent=true, destructive=false, so the safety profile is covered. The description adds useful behavior context the annotations don't: the concrete endpoint, the required v3 version header, and the calendars.write scope. However, it says nothing about update semantics — whether omitted fields are cleared or preserved, or how the variations array replacement behaves — which matters for a PUT on a nested body.

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?

Four short lines with the action front-loaded and no filler prose. The endpoint/version/source metadata is slightly verbose but genuinely informative for an API wrapper, so nothing is really wasted.

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 nested-body mutation with no output schema, the description covers the call mechanics (endpoint, version, auth) and the schema covers every field. The remaining gap is update semantics and result behavior: what the response contains and whether the body is a full replacement, neither of which is addressed.

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% with rich per-field descriptions and examples, so the schema fully documents serviceId and every body field. The description adds no parameter meaning beyond what the schema already provides, making the baseline 3 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 ('Update service by ID') plus the exact HTTP endpoint, so the agent knows precisely what is being mutated and which record is targeted. It does not name how it differs from ghl_calendar_service_create or ghl_calendar_service_update, but the verb+resource pairing 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?

There is no explicit when-to-use, when-not-to-use, or alternative tool named. The 'OAuth scopes: calendars.write' line does imply a prerequisite permission, which is the only usage signal, leaving the agent to infer that this is the edit path for an existing service rather than the create path.

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