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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_update

Idempotent

Update conversation details—including starred status, unread count, and feedback—by conversation ID to keep GoHighLevel conversation records accurate.

Instructions

Update Conversation Update the conversation details based on the conversation ID Endpoint: PUT /conversations/{conversationId} (Version header: v3; source: v3/conversations-v3.json) OAuth scopes: conversations.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": {
      "conversationId": "<conversationId>",
      "body": "<body>"
    },
    "name": "ghl_conversation_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
conversationIdYesConversation ID as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • removedInput schema / properties / body / properties / feedback / description
      Removed value: -"Live chat feedback value for the conversation"
    • removedInput schema / properties / body / properties / feedback / enum
      Removed value: -[
      -  "positive",
      -  "negative"
      -]
    • removedInput schema / properties / body / properties / feedback / example
      Removed value: -"positive"
    • changedInput schema / properties / body / properties / feedback / type
      Previous value: -"string"New value: +"object"
    • addedInput schema / properties / body / title
      Added value: +"UpdateConversationDto"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is largely covered. The description adds useful context beyond that: the exact HTTP verb/path, the required v3 version header, and the OAuth scope conversations.write, which tells the agent about auth requirements. It still says nothing about what happens to omitted fields (partial vs full replacement) despite idempotentHint.

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?

Short and front-loaded with the verb and resource, and the endpoint/scope lines are compact metadata. The redundant title repetition ('Update Conversation') and spec-source provenance are mild filler but not costly.

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 2-parameter mutation with full schema coverage and no output schema, the description plus annotations plus schema give the agent enough to call it correctly. The main missing piece is partial-update semantics for the nested body, which is a minor gap.

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%, so both conversationId and the nested body fields are already documented. The description adds no additional parameter meaning (e.g., whether body fields are optional, or what 'feedback' accepts), so 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 (Update) and resource (Conversation) keyed by conversation ID, and the endpoint line confirms the resource. However, 'details' is generic and doesn't hint at the fields actually writable (starred, feedback, unreadCount), and it offers no differentiation from close siblings like ghl_conversation_update_custom_subtype or ghl_conversation_update_message_status.

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

Usage Guidelines2/5

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

No guidance on when to use this versus the many other conversation update tools in the sibling list, and no preconditions stated beyond the endpoint. The agent must infer selection from naming alone.

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