Skip to main content
Glama
Sign In
ghl-gold

ghl-gold

by MaximKonovalovDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gold_ghl_conversations_list_reply_draft

List recent GoHighLevel conversations, unread first, or fetch a single thread's messages to draft a reply.

Instructions

List recent conversations (unread first) or pull one thread's messages to draft a reply. BYOK. PAID ONLY $39.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gold_ghl_conversations_list_reply_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
location_idNo
conversation_idNoset to fetch messages of one thread

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description discloses useful traits: conversations come 'unread first,' and setting a conversation_id fetches one thread. It does not explicitly state read-only behavior, rate limits, authentication details, or failure modes, so the burden is only partially met.

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?

Two short sentences carry the function, ordering behavior, thread mode, and key access constraints without wasted words. The most important information is front-loaded before the BYOK and pricing caveats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no documentation of return shape, so an agent does not know what list/thread responses look like. The description also omits the role of location_id and limit, which are needed to reliably call the tool.

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 coverage is only 33% and the description does not compensate meaningfully: it implies conversation_id selects a thread, but limit and location_id are left unexplained. The phrase 'pull one thread's messages' adds no detail beyond the schema description already attached to conversation_id.

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 names a clear action and resource: 'List recent conversations' and 'pull one thread's messages to draft a reply,' with an explicit intent. It is specific enough to be understood, though it does not differentiate from siblings like gold_ghl_conversations_ai_summary.

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?

It indicates the intended use ('to draft a reply') and access constraints (BYOK, paid), which helps an agent decide whether it can use it. It does not state when to prefer another tool or when not to use this one, leaving some inference to the agent.

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