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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_group_update

Idempotent

Update an existing calendar group by group ID, including its name, slug, and description, to keep scheduling groups accurate and organized.

Instructions

Update Group Update Group by group ID Endpoint: PUT /calendars/groups/{groupId} (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": {
      "groupId": "<groupId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_group_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / description / description
      Added value: +"Group description"
    • 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: +"GroupUpdateDTO"
  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 readOnly=false, idempotent=true, destructive=false and openWorld=true, so the safety profile is covered. The description adds the required OAuth scope (calendars/groups.write) and API version, which is genuinely useful. It does not disclose that the PUT body requires name, description and slug together, i.e. that this is effectively a full replacement, nor what the response contains.

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?

Short, front-loaded with the action, followed by endpoint and scope metadata. Slight redundancy between 'Update Group' and 'Update Group by group ID', but no wasted prose.

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?

With annotations covering safety and the schema covering the nested body, the essentials are present. However, for a PUT that requires all three fields, the description should say whether omitted fields are cleared or preserved, and there is no output schema to fall back on.

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 both the groupId and all three body fields are already documented in the schema. The description only repeats 'by group ID', adding no semantics beyond the schema. Baseline 3 applies.

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: update a calendar group by group ID. An agent can tell it apart from ghl_calendar_group_create, but nothing distinguishes it from ghl_calendar_group_update_status or explains the scope of the update.

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?

No when-to-use guidance, no prerequisites, no mention of alternatives such as ghl_calendar_group_update_status or ghl_calendar_group_validate_slug. The endpoint and OAuth scope lines are reference metadata, not usage guidance.

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