Skip to main content
Glama
Sign In
GoHighLevel MCP

GoHighLevel MCP

by NerdSnipe-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ghl_get_conversation

Retrieve a GoHighLevel conversation by ID, including all metadata. Use this tool to access specific conversation details for follow-up or analysis.

Instructions

Get a conversation by ID with metadata.

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_get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the operation is a read but adds no context about return behavior, error handling, auth requirements, or what 'metadata' includes. The phrase 'with metadata' is vague and does not clarify expected output or side effects.

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

Conciseness5/5

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

One sentence, front-loaded with verb and resource. No wasted words; it is appropriately concise for the operation it describes.

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?

For a simple get-by-ID operation with one parameter and no output schema, the description is minimally viable but lacks critical behavioral details like return format, error cases, or the nature of metadata. It does not fully compensate for missing annotations and no output schema, but the low complexity keeps it from being inadequate.

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 0%, and the description does not explain the conversationId parameter beyond its name. The name is self-explanatory, but 'with metadata' fails to clarify what is returned regarding the parameter. The description adds minimal value over the schema.

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

Purpose5/5

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

The description uses a specific verb ('Get'), names the resource ('conversation'), and adds scope ('by ID with metadata'). This clearly distinguishes it from sibling tools like ghl_search_conversations and ghl_create_conversation, making the purpose unambiguous.

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?

The description implies usage when you have a specific conversation ID, but it does not explicitly contrast with alternatives like searching or creating conversations. No when-not-to-use guidance is given, so usage context is only implied.

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