GoHighLevel MCP

ghl_create_coupon

Create a discount coupon by specifying code, discount type, and value. Optionally set validity dates, usage limits, and product restrictions.

Instructions

Create a discount coupon.

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": {
      "name": "<name>",
      "code": "<code>",
      "discountType": "<discountType>",
      "discount": "<discount>"
    },
    "name": "ghl_create_coupon"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	Coupon code (e.g. SAVE20)
`name`	Yes
`endDate`	No	Coupon expiry date ISO 8601
`discount`	Yes	Discount value (% or $ amount)
`startDate`	No	Coupon validity start date ISO 8601
`productIds`	No	Restrict to specific product IDs
`usageLimit`	No	Max number of times coupon can be used
`discountType`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

TDQS

C2.9/5.0

Behavior1/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It fails to mention side effects, required permissions, idempotency, validation, or return behavior. The description merely restates the action from the tool name.

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 description is a single, well-formed sentence with no redundancy. It is front-loaded and efficient. However, given the tool's 8 parameters, it is arguably too sparse, but as a concise statement it is effective.

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?

With 8 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain return values, error behavior, usage context, or any nuances of creating a coupon, leaving significant gaps for an agent.

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 75%, so the baseline is 3. The description adds no parameter-level meaning beyond the schema, and the two undocumented parameters (name, discountType) remain unexplained. The schema does most of the heavy lifting.

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 uses the specific verb 'create' and identifies the resource as a 'discount coupon', which clearly distinguishes this tool from siblings like ghl_get_coupons or other create tools. It is unambiguous and acts as a precise verb+resource statement.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description only states the action without any contextual usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server