@nightsquawktech/gohighlevel-mcp-server

Create GoHighLevel Contact Note

ghl_create_contact_note

Add a note to a GoHighLevel contact by providing contact ID and body. Optionally associate with a user.

Instructions

Create a note for a contact with POST /contacts/{contactId}/notes. Write operation: do not run against live data without explicit approval.

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": {
      "contact_id": "<contact_id>",
      "body": "<body>"
    },
    "name": "ghl_create_contact_note"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Note body.
`extra`	No	Optional additional GoHighLevel fields to pass through when the API supports fields not modeled by this tool.
`userId`	No	Optional GoHighLevel user ID associated with the note.
`contact_id`	Yes	Contact ID.
`response_format`	No	Output format: markdown for human-readable summaries, json for structured output.	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Description adds 'Write operation: do not run against live data without explicit approval' beyond annotations, which only indicate write and non-destructive. Provides endpoint context.

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?

Two concise sentences: purpose+endpoint in first, usage warning in second. No wasted words.

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?

Lacks return value description (no output schema). Otherwise adequate for a create tool with well-documented parameters.

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 coverage is 100% with descriptions for all parameters. Description does not add additional parameter meaning beyond the endpoint context.

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?

Clearly states 'Create a note for a contact' with the HTTP endpoint. Distinct from read tools like ghl_get_contact_notes.

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?

Explicitly warns against using on live data without approval. No explicit alternative named, but context is clear.

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

Deploy Server