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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_add_inbound_message

Adds an inbound message to a conversation or contact in GoHighLevel, requiring message body and either conversationId or contactId.

Instructions

Add an inbound message Post the necessary fields for the API to add a new inbound message. Note: Either conversationId or contactId is required Endpoint: POST /conversations/messages/inbound (Version header: v3; source: v3/conversations-v3.json) OAuth scopes: conversations/message.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_conversation_add_inbound_message"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.1.0
    • removedInput schema / properties / body / properties / attachments / example
      Removed value: -[
      -  "https://example.com/files/image.png"
      -]
    • changedInput schema / properties / body / properties / call / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "from": {
      -        "description": "Phone number of the dialer",
      -        "example": "+15037081210",
      -        "type": "string"
      -      },
      -      "status": {
      -        "description": "Call status",
      -        "enum": [
      -          "pending",
      -          "completed",
      -          "answered",
      -          "busy",
      -          "no-answer",
      -          "failed",
      -          "canceled",
      -          "voicemail"
      -        ],
      -        "example": "completed",
      -        "type": "string"
      -      },
      -      "to": {
      -        "description": "Phone number of the receiver",
      -        "example": "+15037081210",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "from": {
      +        "description": "Phone number of the dialer",
      +        "example": "+15037081210",
      +        "type": "string"
      +      },
      +      "status": {
      +        "description": "Call status",
      +        "enum": [
      +          "pending",
      +          "completed",
      +          "answered",
      +          "busy",
      +          "no-answer",
      +          "failed",
      +          "canceled",
      +          "voicemail"
      +        ],
      +        "example": "completed",
      +        "type": "string"
      +      },
      +      "to": {
      +        "description": "Phone number of the receiver",
      +        "example": "+15037081210",
      +        "type": "string"
      +      }
      +    },
      +    "title": "CallDataDTO",
      +    "type": "object"
      +  }
      +]
    • removedInput schema / properties / body / properties / call / example
      Removed value: -{
      -  "from": "+15037081211",
      -  "status": "completed",
      -  "to": "+15037081210"
      -}
    • removedInput schema / properties / body / properties / date / example
      Removed value: -"2024-03-27T18:13:49.000Z"
    • removedInput schema / properties / body / properties / emailMessageId / example
      Removed value: -"rnGyqh2F6uBrIkfhFo9A"
    • removedInput schema / properties / body / properties / emailTo / example
      Removed value: -"recipient@example.com"
    • removedInput schema / properties / body / properties / html / example
      Removed value: -"<p>Hello from the contact.</p>"
    • removedInput schema / properties / body / properties / message / example
      Removed value: -"Hello from the contact."
    • removedInput schema / properties / body / properties / subject / example
      Removed value: -"Welcome email"
    • changedInput schema / properties / body / properties / type / enum
      Previous value: -[
      -  "SMS",
      -  "RCS",
      -  "Email",
      -  "WhatsApp",
      -  "GMB",
      -  "IG",
      -  "FB",
      -  "Custom",
      -  "WebChat",
      -  "Live_Chat",
      -  "Call",
      -  "IVR_Call",
      -  "Campaign_Call",
      -  "Campaign_VoiceMail",
      -  "TIKTOK",
      -  "ALL_IN_ONE_CHAT",
      -  "FORM_SUBMISSION"
      -]New value: +[
      +  "SMS",
      +  "Email",
      +  "WhatsApp",
      +  "GMB",
      +  "IG",
      +  "FB",
      +  "Custom",
      +  "WebChat",
      +  "Live_Chat",
      +  "Call"
      +]
    • changedInput schema / properties / body / required
      Previous value: -[
      -  "type",
      -  "conversationId",
      -  "contactId",
      -  "conversationProviderId"
      -]New value: +[
      +  "type",
      +  "conversationProviderId"
      +]
    • addedInput schema / properties / body / title
      Added value: +"ProcessMessageBodyDto"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose that this is a non-readonly, non-idempotent, open-world write operation. The description adds useful context with the endpoint and OAuth scope, plus the conditional conversationId/contactId requirement, but does not describe side effects, response behavior, or what happens after the inbound message is recorded.

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

Conciseness4/5

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

The description is short and front-loads the core action, endpoint, and key constraint. It wastes some space on the redundant 'Post the necessary fields...' sentence and HTML break tags, but remains appropriately sized.

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?

For a mutation tool with a complex nested body but full schema coverage, the description provides the endpoint, OAuth scope, and the important conversationId-or-contactId constraint. It does not explain type-specific field expectations or post-call behavior, but the schema compensates for most field-level details.

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 description coverage is 100%, so the schema already documents the nested body fields extensively. The description adds a meaningful cross-field constraint not expressed in the schema: either conversationId or contactId is required, which is valuable for correct invocation.

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?

The description states a specific verb and resource: adding a new inbound message via POST /conversations/messages/inbound. It is clear enough to distinguish from generic message creation, but it does not explicitly differentiate itself from close siblings such as ghl_conversation_add_outbound_message or ghl_conversation_send_message.

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?

Usage is implied by 'inbound message' and the disclosed OAuth scope conversations/message.write, but the description does not say when to choose this over sibling message tools or when not to use it. No alternative tool is named despite several message-related siblings.

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