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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_get_email_message

Read-onlyIdempotent

Retrieve a specific email message by its ID from GoHighLevel conversations. Use it to fetch full email content and details when you have the message identifier.

Instructions

Note: the official spec omits the id path-parameter declaration; this server infers it from the URL template (registry.ts fallback added 2026-07-16), so id (the email message ID) is a required argument here despite the spec gap. Get email by Id Endpoint: GET /conversations/messages/email/{id} (Version header: v3; source: v3/conversations-v3.json) OAuth scopes: conversations/message.readonly

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": {
      "id": "<id>"
    },
    "name": "ghl_conversation_get_email_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter (inferred from the URL template; the official spec omits its declaration).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description usefully adds the required OAuth scope (conversations/message.readonly), the API version header, and the source spec file, which are real operational details not present in the annotations. It says nothing about the response payload, but with annotations carrying the safety burden and no output schema, that omission is minor.

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 purpose sentence, endpoint, and scope line are tight and front-loaded enough to be usable. However, the leading paragraph is a long meta-note about a registry fallback and a date stamp, which is implementation trivia that dilutes the primary signal and crowds out more useful guidance.

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 one-parameter read tool with no output schema, the description supplies the endpoint, version header, required scope, and the spec-gap caveat that explains the required argument. Nothing essential to invoking it is missing, though return-value expectations and the relationship to sibling message-getting tools remain unstated.

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% and the single parameter is documented, but the description adds genuine meaning beyond the schema: it explains that `id` is the email message ID and that it is required here because the official spec omits the path-parameter declaration. That resolves a real ambiguity an agent would otherwise hit.

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 ("Get email by Id") and even pins the underlying route GET /conversations/messages/email/{id}, which makes clear it fetches a single email message rather than a generic message. It stops short of naming siblings such as ghl_conversation_get_message or ghl_conversation_get_messages, so the email-vs-generic distinction has to be inferred from the word 'email' and the URL.

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 only implied: the reader can infer this is the call to make when an email message ID is already known, and the stated OAuth scope hints at read access requirements. There is no explicit when-to-use guidance, no exclusions, and no pointer to the sibling tools for listing or fetching non-email messages.

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