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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_get_messages

Read-onlyIdempotent

Retrieve messages from a specific conversation by ID, with optional message-type filtering and pagination to page through complete history.

Instructions

Get messages by conversation id Get messages by conversation id. Endpoint: GET /conversations/{conversationId}/messages (Version header: v3; source: v3/conversations-v3.json) OAuth scopes: conversations/message.readonly Pagination params: lastMessageId, limit — pass them to page through full result sets.

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>"
    },
    "name": "ghl_conversation_get_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoTypes of message to fetched separated with comma
limitNoNumber of messages to be fetched from the conversation. Default limit is 20
lastMessageIdNoMessage ID of the last message in the list as a string
conversationIdYesConversation ID as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "TYPE_CALL",
      -  "TYPE_SMS",
      -  "TYPE_RCS",
      -  "TYPE_EMAIL",
      -  "TYPE_FACEBOOK",
      -  "TYPE_GMB",
      -  "TYPE_INSTAGRAM",
      -  "TYPE_WHATSAPP",
      -  "TYPE_ACTIVITY_APPOINTMENT",
      -  "TYPE_ACTIVITY_CONTACT",
      -  "TYPE_ACTIVITY_INVOICE",
      -  "TYPE_ACTIVITY_PAYMENT",
      -  "TYPE_ACTIVITY_OPPORTUNITY",
      -  "TYPE_LIVE_CHAT",
      -  "TYPE_INTERNAL_COMMENTS",
      -  "TYPE_ACTIVITY_EMPLOYEE_ACTION_LOG",
      -  "TYPE_TIKTOK",
      -  "TYPE_ACTIVITY_WHATSAPP",
      -  "TYPE_FORM_SUBMISSION"
      -]New value: +[
      +  "TYPE_CALL",
      +  "TYPE_SMS",
      +  "TYPE_EMAIL",
      +  "TYPE_FACEBOOK",
      +  "TYPE_GMB",
      +  "TYPE_INSTAGRAM",
      +  "TYPE_WHATSAPP",
      +  "TYPE_ACTIVITY_APPOINTMENT",
      +  "TYPE_ACTIVITY_CONTACT",
      +  "TYPE_ACTIVITY_INVOICE",
      +  "TYPE_ACTIVITY_PAYMENT",
      +  "TYPE_ACTIVITY_OPPORTUNITY",
      +  "TYPE_LIVE_CHAT",
      +  "TYPE_INTERNAL_COMMENTS",
      +  "TYPE_ACTIVITY_EMPLOYEE_ACTION_LOG"
      +]
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the OAuth scope conversations/message.readonly and the pagination semantics — both genuinely useful for an agent planning a call. It stops short of describing ordering or response shape, which keeps it from a 5.

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 content is short but the first sentence is duplicated verbatim, and build-provenance metadata (source: v3/conversations-v3.json) adds little for an agent selecting a tool. The pagination hint is the one genuinely load-bearing sentence.

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 simple read tool with full schema coverage and no output schema, endpoint, auth scope, and pagination guidance cover most of what an agent needs. A brief note on the return shape or default ordering would close the remaining gap, since there is no output schema to fall back on.

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%, setting a baseline of 3, and the description earns a bump by explaining that lastMessageId and limit are the pagination cursor pair to page through full result sets — framing the schema doesn't provide. The `type` enum filter is left unmentioned, though the schema documents it adequately.

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+resource (get messages) scoped by conversation id, which is clear enough to act on. It does not, however, distinguish itself from near-neighbors such as ghl_conversation_get_message (singular), ghl_conversation_get_email_message, or ghl_conversation_search, so an agent must infer from the plural name that this returns a list.

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 the endpoint shape and the note about paging with lastMessageId/limit, which tells the agent how to walk large result sets. There is no explicit when-to-use/when-not statement and no routing to alternative tools for single-message or cross-conversation retrieval.

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