Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

contacts_upsert_contact

Create a new contact or update an existing one in GoHighLevel CRM with detailed fields like name, email, phone, custom data, and duplicate handling.

Instructions

Upsert Contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dndNo
cityNo
nameNo
tagsNoThis field will overwrite all current tags associated with the contact. To update a tags, it is recommended to use the Add Tag or Remove Tag API instead.
emailNo
phoneNo
stateNo
genderNo
sourceNo
countryNo
websiteNo
address1No
lastNameNo
timezoneNo
firstNameNo
assignedToNoUser's Id
locationIdNoDefaults to GHL_LOCATION_ID when omitted.
postalCodeNo
companyNameNo
dateOfBirthNoThe birth date of the contact. Supported formats: YYYY/MM/DD, MM/DD/YYYY, YYYY-MM-DD, MM-DD-YYYY, YYYY.MM.DD, MM.DD.YYYY, YYYY_MM_DD, MM_DD_YYYY
dndSettingsNo
customFieldsNo
inboundDndSettingsNo
createNewIfDuplicateAllowedNoControls whether to create a new contact or update an existing duplicate. **Scenario 1:** If this value is `true` and the location allows duplicate contacts, a new contact will be created immediately without checking for duplicates. **Scenario 2:** If this value is `true` but the location does not a
Behavior2/5

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

Annotations indicate readOnlyHint=false, confirming this is a write operation, but the description adds no behavioral context. It does not disclose potential side effects, such as whether existing data is overwritten, how duplicates are handled, or any permission requirements. Given annotations exist, the bar is lower, but the description still provides zero additional value beyond the bare verb.

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

Conciseness2/5

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

While the description is extremely short, this is under-specification rather than conciseness. A single verb phrase lacks the structure needed to convey functionality. It is not an efficient summary of capabilities but an empty shell.

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

Completeness1/5

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

The tool has 24 parameters, nested objects, no output schema, and low schema coverage. The description is virtually nonexistent, offering no guidance on required vs optional fields, date formats, duplicate handling, or return values. It is completely inadequate for a tool of this complexity.

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

Parameters1/5

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

Schema description coverage is only 21%, so the description must compensate for the many undocumented parameters. However, the description contains no parameter-related information whatsoever. With 24 parameters and many having no schema description, the absence of any explanation leaves agents unable to understand what fields to supply or how they relate to the upsert behavior.

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

Purpose2/5

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

The description 'Upsert Contact' is a direct restatement of the tool name with no additional detail. It does not explain what 'upsert' means, whether it creates, updates, or both, nor does it differentiate from sibling tools like contacts_create_contact or contacts_update_contact. The verb and resource are present, but the description is tautological and fails to provide any meaningful purpose clarification.

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

Usage Guidelines1/5

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

There is zero guidance on when to use this tool versus alternatives. The description does not mention scenarios where an upsert is preferred over a create or update, nor does it reference any prerequisites or exclusions. An agent cannot infer appropriate usage from the description alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIWerk/mcp-server-ghl'

If you have feedback or need assistance with the MCP directory API, please join our Discord server