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

ghl-mcp-server-v2

by zackscriven

ghl_association_create

Create custom associations between contacts, businesses, and custom objects by defining object keys and labels for each side. Use it to link related records in GoHighLevel workflows.

Instructions

Create Association Allow you to create contact - contact , contact - custom objects and business - contact associations, will add more in the future.Documentation Link - https://doc.clickup.com/8631005/d/h/87cpx-293776/cd0f4122abc04d3 Endpoint: POST /associations/ (Version header: v3; source: v3/associations-v3.json) OAuth scopes: associations.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": {
      "body": "<body>"
    },
    "name": "ghl_association_create"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / firstObjectKey / description
      Previous value: -"First Objects Key"New value: +"First Object's Key, e.g. 'custom_objects.children'. (Spec bug override 2026-08-27: empty object schema in upstream spec.)"
    • removedInput schema / properties / body / properties / firstObjectKey / example
      Removed value: -"custom_objects.children"
    • changedInput schema / properties / body / properties / firstObjectKey / type
      Previous value: -"object"New value: +"string"
    • changedInput schema / properties / body / properties / firstObjectLabel / description
      Previous value: -"First Objects Association Label (custom_objects.children)"New value: +"First Object's Association Label, e.g. 'student'. (Spec bug override 2026-08-27: upstream declares this as an empty object schema despite requiring it — the tool was uncallable.)"
    • removedInput schema / properties / body / properties / firstObjectLabel / example
      Removed value: -"student"
    • changedInput schema / properties / body / properties / firstObjectLabel / type
      Previous value: -"object"New value: +"string"
    • changedInput schema / properties / body / properties / secondObjectKey / description
      Previous value: -"Second Objects Key"New value: +"Second Object's Key, e.g. 'contact'. (Spec bug override 2026-08-27: empty object schema in upstream spec.)"
    • removedInput schema / properties / body / properties / secondObjectKey / example
      Removed value: -"contact"
    • changedInput schema / properties / body / properties / secondObjectKey / type
      Previous value: -"object"New value: +"string"
    • changedInput schema / properties / body / properties / secondObjectLabel / description
      Previous value: -"Second Object Association Label (contact)"New value: +"Second Object's Association Label, e.g. 'Teacher'. (Spec bug override 2026-08-27: empty object schema in upstream spec.)"
    • removedInput schema / properties / body / properties / secondObjectLabel / example
      Removed value: -"Teacher"
    • changedInput schema / properties / body / properties / secondObjectLabel / type
      Previous value: -"object"New value: +"string"
    • addedInput schema / properties / body / title
      Added value: +"createAssociationReqDto"
  2. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds genuine value beyond those: the required OAuth scope (associations.write), the exact endpoint and API version, and the fact that only certain object pairs are supported today. It does not say what happens on a duplicate `key` (create-fails vs. upsert), which is the main behavioral unknown for a non-idempotent create.

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

Conciseness3/5

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

Front-loaded with purpose, then link, endpoint, and scopes — reasonable structure. But "Create Association" restates the title already in annotations, "Allow you to create ..." is wordy, and a raw ClickUp documentation URL plus spec-source path consume space without adding call-time value.

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?

No output schema, so the agent gets no signal about what a successful create returns (e.g. the new association id), and the description doesn't fill that gap. For a nested 6-required-field mutation it also doesn't explain that the object keys must already exist or how labels relate to keys, leaving meaningful gaps.

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% — every nested field (key, locationId, first/secondObjectKey, first/secondObjectLabel) carries its own description and examples, so the schema does the work. The description adds nothing about parameter meaning, not even the relationship between object keys and labels, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ("Create Association") and enumerates the association pairs currently supported (contact-contact, contact-custom objects, business-contact). However, it never distinguishes itself from the very confusable sibling ghl_association_create_relation, leaving the agent to infer that this defines an association type while that one links records. Clear purpose, missing sibling differentiation on the one axis that matters most.

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 phrase "Allow you to create contact - contact, contact - custom objects and business - contact associations, will add more in the future" implicitly scopes when the tool is applicable and flags a coverage limitation. But there is no explicit when-not guidance, no mention of prerequisites (the referenced object keys must already exist), and no named alternative such as ghl_association_create_relation or ghl_association_list.

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