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

ghl-mcp-server-v2

by zackscriven

ghl_brand_board_create

Creates a new brand board for a location with logos, colors, and fonts, optionally setting it as default or copying from an existing board.

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.] Create a new brand board Creates a new brand board with logos, colors, and fonts Endpoint: POST /brand-boards/ (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": {
      "body": "<body>"
    },
    "name": "ghl_brand_board_create"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 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"
      +]
    • changedInput schema / properties / body / properties / type / enum
      Previous value: -[
      -  "template",
      -  "blank",
      -  "snapshot",
      -  "url"
      -]New value: +[
      +  "template",
      +  "blank",
      +  "snapshot"
      +]
    • removedInput schema / properties / body / properties / url
      Removed value: -{
      -  "description": "Website URL to extract design kit from (colors, fonts, logos)",
      -  "example": "https://example.com",
      -  "type": "string"
      -}
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world, non-idempotent operation. The description adds meaningful context beyond annotations: legacy/deprecation status, Version header, endpoint path, Sub-Account token requirement, and OAuth scope.

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 definition is reasonably compact and includes the important legacy warning up front. It repeats the create purpose slightly and mixes endpoint/auth metadata into the description, but every line is relevant and no major text is wasted.

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 complex nested create operation, the description supplies legacy status, endpoint, version header, auth token type, and OAuth scope, while the schema covers all parameters in detail. It does not describe the response shape or all side effects, but it is largely complete for invocation.

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%, including nested details for logos, colors, fonts, default, parentId, and brandBoardId. The description only summarizes that logos, colors, and fonts are included, adding little beyond the already-rich schema, so the baseline 3 is appropriate.

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

Purpose5/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 a new brand board' and 'Creates a new brand board with logos, colors, and fonts.' It clearly distinguishes creation from sibling operations such as get, update, and delete.

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?

It provides useful usage context by warning that this is a legacy fallback and recommending a current equivalent, plus notes the required Sub-Account token and OAuth scope. However, it does not name the current equivalent or specify concrete when-to-use conditions versus alternatives.

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