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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_ai_get_generation

Read-onlyIdempotent

Retrieves detailed generation data for an AI message by message ID and source, including system prompt, conversation history, knowledge base, website, FAQ, and rich text chunks.

Instructions

Get the generation details Retrieves detailed information about AI responses including the System Prompt, Conversation history, Knowledge base, website, FAQ chunks, and Rich Text chunks. Endpoint: GET /conversation-ai/generations (Version header: v3; source: v3/conversation-ai-v3.json) OAuth scopes: conversation-ai.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": {
      "messageId": "<messageId>",
      "source": "<source>"
    },
    "name": "ghl_conversation_ai_get_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesSource of the AI message - conversation or workflow
messageIdYesMessage Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / source / description
      Added value: +"Source of the AI message - conversation or workflow"
  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 declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real context beyond them: the required OAuth scope (conversation-ai.readonly), the API version header, and the underlying source spec - all of which affect whether a call will succeed.

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

Conciseness4/5

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

Front-loaded purpose sentence followed by a compact enumeration of returned content, then endpoint/scope metadata on separate lines. Minor redundancy between the title-like opener 'Get the generation details' and the following sentence, but no filler overall.

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?

There is no output schema, so the description's list of returned chunks (system prompt, history, KB, FAQ/Rich Text) is doing meaningful work in telling the agent what to expect back. Endpoint, version and scope are also supplied. Only the sibling-disambiguation is missing.

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

Parameters3/5

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

Schema description coverage is 100%: both messageId and the source enum are documented in the schema, including the 'conversation or workflow' meaning of source. The description adds nothing further about the parameters, which is the baseline 3 case.

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?

Specific verb+resource ('Retrieves detailed information about AI responses ... generation details') with an enumeration of what is returned (System Prompt, conversation history, KB/website/FAQ/Rich Text chunks). It does not differentiate itself from proximity siblings such as ghl_conversation_get_message or ghl_conversation_get_messages, which an agent could plausibly pick by mistake.

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: an agent can infer this is for inspecting how a specific AI message was generated from the enumerated contents. There is no explicit 'use this when you need X, use ghl_conversation_get_message instead' routing.

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