Skip to main content
Glama
Sign In
GoHighLevel MCP

GoHighLevel MCP

by NerdSnipe-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ghl_get_coupons

Retrieve discount coupons from a GoHighLevel location. Filter by name, code, or status, and control results with limit and offset.

Instructions

Get discount coupons in the location.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghl_get_coupons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNoSearch by coupon name or code
statusNoFilter by coupon status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic action, failing to mention pagination (limit/offset), filtering, or what the response contains. This is insufficient for a list operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the core purpose. Every word adds value with no redundancy or irrelevant detail.

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?

Given the tool has four parameters and no output schema, the description is too sparse. It does not explain the list behavior, return format, or the meaning of 'location,' leaving significant gaps for an agent to select and invoke the tool correctly.

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 description coverage is only 50% (search and status have descriptions, but limit and offset do not). The description adds no parameter information, failing to compensate for the missing schema details. The unannotated parameters remain unclear.

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 clearly states the action (get), the resource (discount coupons), and the scope (in the location). It is specific enough to distinguish from sibling tools like create_coupon or get_orders.

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?

The description implies usage for retrieving coupons but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusion criteria. The context is clear from the name, but no additional guidance is given.

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