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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_update_message_status

Idempotent

Updates a message's delivery status (delivered, failed, pending, or read) in GoHighLevel conversations, helping track delivery outcomes and provider errors.

Instructions

Update message status Post the necessary fields for the API to update message status. Endpoint: PUT /conversations/messages/{messageId}/status (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": {
      "messageId": "<messageId>",
      "body": "<body>"
    },
    "name": "ghl_conversation_update_message_status"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / error / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "code": {
      -        "description": "Error Code",
      -        "example": "1",
      -        "type": "string"
      -      },
      -      "message": {
      -        "description": "Error Message",
      -        "example": "There was an error from the provider",
      -        "type": "string"
      -      },
      -      "type": {
      -        "description": "Error Type",
      -        "example": "saas",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "code",
      -      "type",
      -      "message"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "code": {
      +        "description": "Error Code",
      +        "example": "1",
      +        "type": "string"
      +      },
      +      "message": {
      +        "description": "Error Message",
      +        "example": "There was an error from the provider",
      +        "type": "string"
      +      },
      +      "type": {
      +        "description": "Error Type",
      +        "example": "saas",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "type",
      +      "message"
      +    ],
      +    "title": "ErrorDto",
      +    "type": "object"
      +  }
      +]
    • removedInput schema / properties / body / properties / error / example
      Removed value: -{
      -  "message": "There was an error from the provider",
      -  "type": "saas"
      -}
    • removedInput schema / properties / body / properties / recipients / example
      Removed value: -[
      -  {
      -    "emailId": "john@doe.com",
      -    "status": "delivered"
      -  }
      -]
    • addedInput schema / properties / body / title
      Added value: +"UpdateMessageStatusDto"
  2. First observedv2.0.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive and open-world, so safety is covered; the description adds the concrete OAuth scope (conversations/message.write), which is genuine extra context. It does not explain status-transition semantics, whether prior statuses can be overwritten, or what happens to the optional error/recipients fields.

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?

It is short, but the second line ('Post the necessary fields for the API to update message status') is pure filler duplicating line one, while the genuinely useful endpoint and OAuth details sit after it rather than being front-loaded.

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?

With full schema coverage and annotations in place, the description only needs to add routing and behavioral nuance; it supplies the write scope but leaves the sibling ambiguity (message vs email message status) unresolved, which is the main thing an agent needs here.

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

Parameters2/5

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

Schema description coverage is 100% and every field including the nested DTO, enum values and error object is documented in the schema, so the baseline would be 3. The description adds nothing — 'post the necessary fields' restates the requirement without clarifying messageId scope or how body.status interacts with optional email fields, so it falls below baseline.

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

Purpose3/5

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

It names a specific verb and resource (update a message's status), but the opening two lines are essentially the tool name restated, and it never distinguishes this from the near-identical sibling ghl_conversation_update_email_message_status — an agent must inspect both schemas to know which applies.

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?

There is no when-to-use guidance: no preconditions, no exclusions, and no pointer to an alternative. The endpoint and version-header metadata describe wiring, not when an agent should choose this tool over the email-status sibling.

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