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

ghl-mcp-server-v2

by zackscriven

ghl_brand_board_set_default_voice

Set a brand voice as the default for a location, automatically unsetting the previous default.

Instructions

Set Default Brand Voice Set a brand voice as the default for a location. The previous default will be unset. Endpoint: POST /brand-boards/locations/{locationId}/brand-voices/{brandVoiceId}/default (Version header: v3; source: v3/brand-boards-v3.json) Requires a Sub-Account (location) token. OAuth scopes: brand-boards/voices.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>",
      "brandVoiceId": "<brandVoiceId>"
    },
    "name": "ghl_brand_board_set_default_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation ID
brandVoiceIdYesBrand voice ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 only declare that this is a non-read-only, non-destructive mutation; the description adds the material side effect that the previously set default is implicitly unset, plus the required token type and OAuth scope. That is real value beyond annotations, though it doesn't address failure modes (e.g. invalid brandVoiceId) or whether the change can be reverted.

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 behavior sentence is front-loaded before endpoint/auth metadata, and every line carries information. The only waste is the leading title restatement ("Set Default Brand Voice") duplicating the tool name.

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 2-parameter mutation with full schema coverage and no output schema, the description covers purpose, side effect, token type, and scope. What remains unsaid — the response body and whether callers must verify the new default — is minor at this complexity.

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 locationId and brandVoiceId are already documented. The description only echoes them through the endpoint path and prose, adding no format or constraint detail beyond the schema. 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?

A specific verb and resource ("Set a brand voice as the default for a location") plus the key distinguishing consequence ("The previous default will be unset") separate it cleanly from sibling voice tools like update_voice or create_voice. An agent can select it without opening the schema.

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?

Prerequisites are stated (Sub-Account/location token, brand-boards/voices.write scope), which implies the correct calling context, but the description never says when to choose this over update_voice or how it relates to listing voices first. Usage is inferable rather than explicit.

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