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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_get_message_transcription

Read-onlyIdempotent

Retrieve a message's recording transcription by message ID and location ID. Use it to read or process the transcript for a specific conversation message.

Instructions

Get transcription by Message ID Get the recording transcription for a message by passing the message id Endpoint: GET /conversations/locations/{locationId}/messages/{messageId}/transcription (Version header: v3; source: v3/conversations-v3.json) Requires a Sub-Account (location) token.

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": {
      "locationId": "<locationId>",
      "messageId": "<messageId>"
    },
    "name": "ghl_conversation_get_message_transcription"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYesMessage ID as string
locationIdYesLocation ID as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful operational context by naming the endpoint, version header, and token type, but it does not disclose return behavior or what happens when no transcription exists.

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?

The description is short and front-loaded with the core action. It has minor redundancy between the first two lines, but the endpoint and authorization note are compact and useful.

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 parameter coverage and rich annotations, the description supplies the missing operational details: endpoint, API version, and required token type. It omits return-value details, but the overall context is sufficient to invoke the tool correctly.

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%, so both locationId and messageId are already documented in the schema. The description only restates that the message ID is passed in, without adding syntax, constraints, or examples beyond 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 states a specific verb and resource: get the recording transcription for a message by message ID. It clearly distinguishes this from adjacent conversation tools such as ghl_conversation_get_message_recording and ghl_conversation_download_message_transcription.

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 clearly enough: call this with a message ID when you need a transcription. However, it does not explicitly say when to choose this over download_message_transcription or get_message_recording, nor does it state any exclusions or preconditions beyond the required token.

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