Skip to main content
Glama
Sign In
zackscriven

ghl-mcp-server-v2

by zackscriven
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ghl_brand_board_update_voice

Updates an existing brand voice by ID for a location, revising details such as name, tone, audience, and brand values.

Instructions

Update Brand Voice Update a brand voice by ID Endpoint: PATCH /brand-boards/locations/{locationId}/brand-voices/{brandVoiceId} (Version header: v3; source: v3/brand-boards-v3.json) Requires a Sub-Account (location) token. OAuth scopes: brand-boards/voices.write

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation ID
brandVoiceIdYesBrand voice ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / answers / allOf
      Previous value: -[
-  {
-    "properties": {
-      "brandName": {
-        "description": "Brand Name",
-        "example": "Acme Inc",
-        "type": "string"
-      },
-      "brandPromise": {
-        "description": "Brand Promise",
-        "example": "We deliver on time, every time",
-        "type": "string"
-      },
-      "brandPurpose": {
-        "description": "Brand Purpose",
-        "example": "To empower small businesses with technology",
-        "type": "string"
-      },
-      "brandValues": {
-        "description": "Brand Values",
-        "example": "Integrity, Excellence, Innovation",
-        "type": "string"
-      },
-      "businessHours": {
-        "description": "Business Hours",
-        "example": "Mon-Fri 9am-5pm",
-        "type": "string"
-      },
-      "businessType": {
-        "description": "Business Type",
-        "example": "Software Development",
-        "type": "string"
-      },
-      "callToAction": {
-        "description": "Call to Action",
-        "example": "Schedule a demo today",
-        "type": "string"
-      },
-      "companyAddress": {
-        "description": "Company Address",
-        "example": "123 Main St, Anytown, CA",
-        "type": "string"
-      },
-      "companyEmail": {
-        "description": "Company Email",
-        "example": "contact@example.com",
-        "type": "string"
-      },
-      "companyWebsite": {
-        "description": "Company Website",
-        "example": "https://example.com",
-        "type": "string"
-      },
-      "competitiveAdvantage": {
-        "description": "Competitive Advantage",
-        "example": "Proprietary AI technology",
-        "type": "string"
-      },
-      "customerPainPoints": {
-        "description": "Customer Pain Points",
-        "example": "Difficulty with time management",
-        "type": "string"
-      },
-      "phone": {
-        "description": "Phone Information",
-        "example": {
-          "countryCode": "US",
-          "phoneNumber": "5551234567"
-        },
-        "type": "object"
-      },
-      "risksOfInaction": {
-        "description": "Risks of Inaction",
-        "example": "Falling behind competitors",
-        "type": "string"
-      },
-      "targetAudience": {
-        "description": "Target Audience",
-        "example": "Small business owners",
-        "type": "string"
-      },
-      "toneOfVoice": {
-        "description": "Tone of Voice",
-        "example": "Professional and friendly",
-        "type": "string"
-      },
-      "uniqueSellingProposition": {
-        "description": "Unique Selling Proposition",
-        "example": "The only solution that integrates with all major platforms",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "brandName": {
+        "description": "Brand Name",
+        "example": "Acme Inc",
+        "type": "string"
+      },
+      "brandPromise": {
+        "description": "Brand Promise",
+        "example": "We deliver on time, every time",
+        "type": "string"
+      },
+      "brandPurpose": {
+        "description": "Brand Purpose",
+        "example": "To empower small businesses with technology",
+        "type": "string"
+      },
+      "brandValues": {
+        "description": "Brand Values",
+        "example": "Integrity, Excellence, Innovation",
+        "type": "string"
+      },
+      "businessHours": {
+        "description": "Business Hours",
+        "example": "Mon-Fri 9am-5pm",
+        "type": "string"
+      },
+      "businessType": {
+        "description": "Business Type",
+        "example": "Software Development",
+        "type": "string"
+      },
+      "callToAction": {
+        "description": "Call to Action",
+        "example": "Schedule a demo today",
+        "type": "string"
+      },
+      "companyAddress": {
+        "description": "Company Address",
+        "example": "123 Main St, Anytown, CA",
+        "type": "string"
+      },
+      "companyEmail": {
+        "description": "Company Email",
+        "example": "contact@example.com",
+        "type": "string"
+      },
+      "companyWebsite": {
+        "description": "Company Website",
+        "example": "https://example.com",
+        "type": "string"
+      },
+      "competitiveAdvantage": {
+        "description": "Competitive Advantage",
+        "example": "Proprietary AI technology",
+        "type": "string"
+      },
+      "customerPainPoints": {
+        "description": "Customer Pain Points",
+        "example": "Difficulty with time management",
+        "type": "string"
+      },
+      "phone": {
+        "description": "Phone Information",
+        "example": {
+          "countryCode": "US",
+          "phoneNumber": "5551234567"
+        },
+        "type": "object"
+      },
+      "risksOfInaction": {
+        "description": "Risks of Inaction",
+        "example": "Falling behind competitors",
+        "type": "string"
+      },
+      "targetAudience": {
+        "description": "Target Audience",
+        "example": "Small business owners",
+        "type": "string"
+      },
+      "toneOfVoice": {
+        "description": "Tone of Voice",
+        "example": "Professional and friendly",
+        "type": "string"
+      },
+      "uniqueSellingProposition": {
+        "description": "Unique Selling Proposition",
+        "example": "The only solution that integrates with all major platforms",
+        "type": "string"
+      }
+    },
+    "title": "UpdateBrandVoiceAnswersDto",
+    "type": "object"
+  }
+]
    • addedInput schema / properties / body / title
      Added value: +"UpdateBrandVoicePublicV1BodyDto"
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-destructive, non-idempotent, open-world behavior. The description adds real value beyond that: the concrete PATCH path, the v3 version header, the spec source file, the required Sub-Account token, and the brand-boards/voices.write OAuth scope. It does not mention that the update is a partial/field-level merge, which is the one meaningful gap.

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?

Front-loaded with the action, followed by endpoint, then auth and scope. The endpoint line bundles version and source provenance which is slightly noisy, but overall it is tight and nothing is redundant.

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 mutation with no output schema, the description covers auth, scope, routing, and version — the details an agent needs to construct a valid call. Missing only update-semantics (partial vs full replacement of the body) and error behavior, which are minor against a fully documented body schema.

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 descriptions and examples for every field in the nested body object, so the schema carries the semantics. The description contributes only the path placement of locationId and brandVoiceId, which is the baseline expectation when schema coverage is high.

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+resource ("Update a brand voice by ID") and the exact endpoint, so it is clearly distinguishable from create_voice, delete_voice, and get_voice siblings. It stops short of explicitly naming those siblings or contrasting behavior.

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?

Implied usage only — the word "Update" plus the "Requires a Sub-Account (location) token" prerequisite tells an agent when it is callable, but there is no explicit when-to-use guidance, no exclusions, and no reference to the sibling get/create/delete voice tools.

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