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

ghl-mcp-server-v2

by zackscriven

ghl_brand_board_delete

DestructiveIdempotent

Deletes a Brand Board in a GoHighLevel sub-account by location ID and brand board ID using the legacy API endpoint.

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.] Delete a Brand Board Deletes a Brand Board Endpoint: DELETE /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>"
    },
    "name": "ghl_brand_board_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBrand board ID to update, retrieve, or delete
locationIdYesLocation ID where the brand board exists

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry destructiveHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds material context beyond that: it requires a Sub-Account (location) token and the brand-boards/design-kit.write OAuth scope, and it pins the legacy Version header — all things an agent cannot infer from annotations.

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 deprecation warning is correctly front-loaded before the operation statement, and the endpoint/auth/scope lines are dense and useful. Slight waste in the redundant 'Delete a Brand Board / Deletes a Brand Board' pair that merely restates the title twice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter delete with no output schema, the description supplies everything an agent needs to decide and invoke: deprecation status, endpoint shape, token type, and required OAuth scope. Nothing material is left unspecified.

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 both parameters have descriptions plus examples, so the schema does the heavy lifting. The description adds only the indirect hint that locationId must correspond to a Sub-Account token, which is marginal beyond the schema baseline.

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?

States a specific verb and resource ('Delete a Brand Board') and reinforces it with the concrete endpoint DELETE /brand-boards/{locationId}/{id}. Distinguishes it from sibling brand-board operations (get_by_id, update, create) by naming the exact resource path.

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?

Explicitly frames the when-not: the LEGACY FALLBACK banner says the endpoint is gone from live v3 docs, expects removal, and advises preferring a current equivalent. It does not name the specific replacement tool, so the agent still has to guess which sibling to use, but the deprecation context is unusually clear.

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