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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_get_message_recording

Read-onlyIdempotent

Fetch a message recording as raw audio/x-wav by message ID and location ID; handle the binary WAV response instead of parsing JSON.

Instructions

Response is NOT JSON — returns the raw recording as audio/x-wav (Content-Disposition: attachment; filename=audio.wav) per the spec's response headers. Callers must handle a binary/audio body, not a parsed JSON object. Get Recording by Message ID Get the recording for a message by passing the message id Endpoint: GET /conversations/messages/{messageId}/locations/{locationId}/recording (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_recording"
  }
}

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

A4.4/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing the non-JSON response format, the exact audio/x-wav content type, the Content-Disposition filename, and the Sub-Account token requirement. These are critical behavioral details for correctly handling the response and authenticating the call.

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 most important fact — that the response is raw audio, not JSON — is front-loaded effectively. There is some redundancy from restating the title and resource description after the response warning, but the overall text remains focused and reasonably compact.

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

Completeness5/5

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

For a read-only binary retrieval tool with no output schema, the description covers the essentials: the endpoint, required token type, input identifiers, and the unexpected binary return format. An agent has enough information to invoke the tool and correctly handle its response.

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 messageId and locationId are already documented in the input schema. The description reinforces that the message ID is passed to identify the recording and places both parameters in the endpoint path, but it does not add substantial semantic detail 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: retrieve the recording for a message by message ID, with the exact endpoint path. It is clearly distinguishable from transcript-related siblings because it says 'recording' and repeatedly emphasizes the audio/wav response rather than parsed message content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: callers pass a message ID and location ID to fetch the raw recording, and they must be prepared for a binary/audio body. However, it does not explicitly contrast this with sibling tools such as ghl_conversation_get_message_transcription or ghl_conversation_download_message_transcription, so the agent must infer when to use recording versus transcription.

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