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

ghl-mcp-server-v2

by zackscriven

ghl_business_update

Idempotent

Update a business's profile details, such as name, contact information, address, and website, by business ID. Use it to keep GoHighLevel business records current.

Instructions

Update Business Endpoint: PUT /businesses/{businessId} (Version header: v3; source: v3/businesses-v3.json) OAuth scopes: businesses.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": {
      "businessId": "<businessId>",
      "body": "<body>"
    },
    "name": "ghl_business_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdateBusinessDto"
  2. First observedv2.0.0

TDQS

C2.7/5.0
Behavior3/5

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

The description adds the required OAuth scope (businesses.write) and API version header, which the annotations do not convey and which matters for auth setup. Beyond that it discloses nothing about update semantics, e.g. whether omitted fields are cleared or preserved, which is the key behavioral unknown for a partial-update PUT.

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?

Three compact lines with the action front-loaded and endpoint metadata after it. The OpenAPI source path (v3/businesses-v3.json) is developer-facing noise rather than agent-useful context, keeping it off a 5.

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

Completeness2/5

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

For a mutation tool with a nested ten-field body, no output schema, and no annotations covering update semantics, the description is thin. It omits what happens on invalid IDs, whether the update is full or partial, and what a success response contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% and the description adds no meaning for either parameter. The nested body's ten updatable fields and the undocumented businessId are left entirely to the schema, with no guidance on which fields are required or how nulls are handled.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the verb and resource ("Update Business") and adds the underlying endpoint, so an agent knows this mutates an existing business. It does not say what aspects of the business can be changed, and the only differentiation from siblings like ghl_business_create/get comes from the name itself.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus ghl_business_create or ghl_business_get, nor any prerequisite or partial-update caveat. The agent must infer usage purely from the tool name and HTTP method.

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