Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_contact_upsert

Upsert a contact: create new or update existing by matching email or phone, with configurable duplicate handling.

Instructions

Requires locationId. Same field set as ghl_contact_create; use createNewIfDuplicateAllowed to control dedup behavior. Upsert Contact The Upsert API will adhere to the configuration defined under the "Allow Duplicate Contact" setting at the Location level. If the setting is configured to check both Email and Phone, the API will attempt to identify an existing contact based on the priority sequence specified in the setting, and will create or update the contact accordingly.If two separate contacts already exist—one with the same email and another with the same phone—and an upsert request includes both the email and phone, the API will update the contact that matches the first field in the configured sequence, and ig Endpoint: POST /contacts/upsert (Version header: v3; source: v3/contacts-v3.json) OAuth scopes: contacts.write

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
Behavior4/5

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

The description discloses behavioral traits beyond annotations, such as the dedup behavior adhering to location-level settings, the effect of createNewIfDuplicateAllowed, and that tags overwrite all current tags. No annotation contradictions (readOnlyHint=false is consistent with mutation).

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?

The description is front-loaded with key information but is somewhat lengthy and includes HTML formatting and truncation. It could be more concise without losing essential details.

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

Completeness4/5

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

Given the complexity (nested objects, custom fields, DND settings), the description covers important behavioral aspects like dedup control and tags overwriting. It includes endpoint and OAuth scopes but lacks details on return values or error cases. No output schema exists, so the description carries the burden.

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

Parameters4/5

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

Schema coverage is 100% with parameter descriptions. The description adds value by explaining the createNewIfDuplicateAllowed scenarios in detail, but much of the parameter information is already in the schema. The description provides additional context on dedup logic.

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 'Upsert Contact' and explains that it requires locationId, uses the same field set as ghl_contact_create, and controls dedup via createNewIfDuplicateAllowed. It distinguishes from sibling tools like ghl_contact_create and ghl_contact_update by its upsert behavior.

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

Usage Guidelines4/5

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

The description gives explicit usage context: requires locationId, same field set as create, and provides scenarios for createNewIfDuplicateAllowed. However, it does not explicitly state when not to use this tool or mention alternatives beyond ghl_contact_create.

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/zackscriven/ghl-mcp-server'

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