Skip to main content
Glama
KaiCalls MCP Server

KaiCalls MCP Server

Official

Get Transcript

get_transcript
Read-onlyIdempotent

Retrieve a completed call's transcript, summary, and insights—including lead score, sentiment, intake answers, talk time, and lead journey—using its call ID.

Instructions

Get the transcript and summary of a completed call, plus its insights: Kai's lead score for the call, the caller's sentiment, the intake answers collected, who did the talking, and the lead journey (channel, landing page, first contact, number of calls).

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": {
      "call_id": "<call_id>"
    },
    "name": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
call_idYesThe call ID to get the transcript for

Output Schema

NameRequiredDescriptionDefault
callNo
errorNoPresent when success is false
successYesWhether the tool completed successfully
insightsNo
transcriptNo
transcript_lengthNo
transcript_availableNo
transcript_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 and closed-world, so the safety profile is covered. The description adds a real behavioral constraint beyond that — it only applies to completed calls — and itemizes what the agent will receive. It does not describe failure behavior for pending calls or any latency/size considerations.

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?

One sentence, front-loaded with the core action and resource before the enumeration of insights. The trailing list is fairly long and partly overlaps what the output schema would reveal, but it earns its place as selection signal.

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 single-parameter read tool with full schema coverage, full annotations, and an output schema, the description covers enough to call it correctly. The remaining gap is routing guidance against adjacent read tools and what happens for non-completed calls.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains call_id fully. The description adds no format, source, or acquisition guidance for the ID, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get the transcript and summary of a completed call') and enumerates the payload (lead score, sentiment, intake answers, talk-time, lead journey), which makes it distinguishable from recording/conversation-style siblings. It stops short of naming any sibling explicitly, so the differentiation is inferred from the content list rather than stated.

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 phrase 'of a completed call' implicitly scopes usage to calls that have already ended, which is useful eligibility guidance. However, there is no explicit when-to-use, no exclusion for in-progress calls' error behavior, and no pointer to alternatives such as fetching a recording or requesting a webhook instead.

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