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

ghl-mcp-server-v2

by zackscriven

ghl_brand_board_update

Update an existing brand board's name, fonts, logos, colors, and default status using location and board IDs. Requires a sub-account token.

Instructions

[LEGACY FALLBACK — this endpoint is no longer in the live v3 docs (checked 2026-10-28) but is still served under the legacy Version header. Expect removal; prefer a current equivalent.] Update a Brand Board Updates an existing Brand Board Endpoint: PATCH /brand-boards/{locationId}/{id} (Version header: 2021-07-28; source: brand-boards.json) Requires a Sub-Account (location) token. OAuth scopes: brand-boards/design-kit.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": {
      "locationId": "<locationId>",
      "id": "<id>",
      "body": "<body>"
    },
    "name": "ghl_brand_board_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBrand board ID to update, retrieve, or delete
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation ID where the brand board exists

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.1.0
    • removedInput schema / properties / body / properties / colors / example
      Removed value: -[
      -  {
      -    "hex": "#FF5733",
      -    "hexa": "#FF5733FF",
      -    "label": "Brand Orange",
      -    "rgb": "rgb(255, 87, 51)",
      -    "rgba": "rgba(255, 87, 51, 1)"
      -  }
      -]
    • changedInput schema / properties / body / properties / colors / items / properties / hexa / description
      Previous value: -"Color in 8-digit hexadecimal notation with alpha channel"New value: +"Color in HEXA format (with alpha)"
    • changedInput schema / properties / body / properties / colors / items / properties / rgba / description
      Previous value: -"Color with red, green, blue, and alpha channel values"New value: +"Color in RGBA format"
    • changedInput schema / properties / body / properties / colors / items / required
      Previous value: -[
      -  "hexa",
      -  "rgba",
      -  "hex",
      -  "rgb",
      -  "label"
      -]New value: +[
      +  "id",
      +  "hexa",
      +  "rgba",
      +  "hex",
      +  "rgb",
      +  "label"
      +]
    • removedInput schema / properties / body / properties / fonts / example
      Removed value: -[
      -  {
      -    "fallback": "sans-serif",
      -    "font": "Montserrat",
      -    "label": "Heading Font"
      -  }
      -]
    • changedInput schema / properties / body / properties / fonts / items / required
      Previous value: -[
      -  "font",
      -  "fallback",
      -  "label"
      -]New value: +[
      +  "id",
      +  "font",
      +  "fallback",
      +  "label"
      +]
    • removedInput schema / properties / body / properties / logos / example
      Removed value: -[
      -  {
      -    "label": "Primary Logo",
      -    "path": "/locations/ve9EPM428h8vShlRW1KT/logos/my-logo.png",
      -    "url": "https://storage.googleapis.com/bucket/logos/my-logo.png"
      -  }
      -]
    • changedInput schema / properties / body / properties / logos / items / required
      Previous value: -[
      -  "url",
      -  "label",
      -  "path"
      -]New value: +[
      +  "id",
      +  "url",
      +  "label",
      +  "path"
      +]
  2. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds material context the annotations cannot convey: deprecation status, the required Version header, that a Sub-Account (location) token is mandatory, and the exact OAuth scope brand-boards/design-kit.write. It does not address the notable idempotentHint=false on a PATCH, nor whether omitted body fields are preserved or cleared.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The most decision-relevant fact, the deprecation warning, is front-loaded in brackets before anything else. The remaining lines are compact metadata (endpoint, version, auth, scope) with only the minor redundancy of "Update a Brand Board" / "Updates an existing Brand Board" restating the same thing twice.

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 mutating tool with no output schema and a nested request body, the description supplies the operational essentials: endpoint shape, version header, token type and OAuth scope. The one meaningful gap is update semantics — whether sending a partial body preserves or wipes existing fonts/logos/colors — which an agent calling a PATCH needs to know.

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 (name, fonts, logos, colors, default, parentId) is fully documented inline, so the schema does the heavy lifting. The description contributes nothing about parameter behavior — notably whether arrays are replaced wholesale or merged — so the 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?

The description names a specific verb and resource ("Update a Brand Board", "Updates an existing Brand Board") and pins the exact endpoint PATCH /brand-boards/{locationId}/{id}, so there is no ambiguity about the operation. It is distinguishable from ghl_brand_board_create / _get_by_id / _delete by the verb, though it never explicitly contrasts itself with the close siblings ghl_brand_board_update_design_kit or ghl_brand_board_update_voice.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The leading legacy banner gives real when-not-to-use guidance: the endpoint is absent from live v3 docs, is served only under the 2021-07-28 Version header, and callers should "prefer a current equivalent." That is strong steering away from the tool, but the guidance stops short of naming the replacement tool or stating the condition under which the legacy path must be used anyway.

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