GoHighLevel MCP

ghl_create_trigger_link

Create a clickable trigger link that fires an action and redirects to a specified URL for GoHighLevel automation.

Instructions

Create a trigger link that fires an action when clicked.

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>",
      "redirectTo": "<redirectTo>"
    },
    "name": "ghl_create_trigger_link"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Link name
`redirectTo`	Yes	URL to redirect to after trigger

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

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 does not mention potential side effects, permissions required, reversibility, or what the return value is. The only behavioral detail is that the link fires an action when clicked, which is minimal.

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 sentence, concise and front-loaded, with no redundant information. Every word contributes to the purpose.

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

Completeness3/5

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

Given the simplicity of the tool (only 2 parameters, both described in schema), the description is minimally adequate. However, with no output schema, it fails to mention what is returned after creation, which is a gap for an agent expecting a result.

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?

The schema already covers both parameters (name and redirectTo) with descriptions, achieving 100% coverage. The tool description adds no additional meaning beyond the schema, so the baseline of 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?

The description clearly identifies the action (Create) and the resource (trigger link), and specifies the behavior ('fires an action when clicked'). This distinguishes it from sibling tools like ghl_get_trigger_links and ghl_delete_trigger_link.

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?

The description does not provide any guidance on when to use this tool vs alternatives, nor does it mention exclusions, prerequisites, or related tools. It simply states what the tool does, leaving the agent to infer usage context.

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

Deploy Server