Feature: Add get_call_transcript Tool#8
Conversation
… of a specific call
…e optional properties
feat: enhance message transformation in CallTranscriptOutput to handle optional properties
Co-authored-by: RP <rpiloto@vitruvix.com>
Co-authored-by: RP <rpiloto@vitruvix.com>
|
Tested the MCP server with these changes, works perfectly. |
|
@stevenbdf any reason this hasn't been merged? It's properly implemented and follows your existing architecture. |
|
@ramsrib any reason this hasn't been merged? |
|
bumping this, any reason this hasn’t been merged? |
|
@youngfreshunique No idea. It's been a long time since I contributed to this. It seems there are conflicts now. |
|
Still happening. Hitting this in a Claude Code agent that places outbound calls then needs |
This pull request introduces a new tool,
get_call_transcript, to the Vapi MCP server. This tool allows users to retrieve the full transcript.The existing
get_calltool only returns basic metadata about a call, omitting the rich conversational data that is crucial for analyzing and improving AI assistant prompts.Implementation
The implementation follows the existing architecture of the MCP server to ensure consistency and maintainability:
Schema Definition (
src/schemas/index.ts):CallTranscriptOutputSchemawas created to define the shape of the detailed call data.GetCallTranscriptInputSchemawas added, reusing the existingGetCallInputSchema.Transformer Function (
src/transformers/index.ts):transformCallTranscriptOutputfunction was implemented to map the fullVapi.Callobject to the new schema, extracting the transcript, messages, and other details.Tool Registration (
src/tools/call.ts):get_call_transcripttool was registered, using the new schema and transformer. It leverages the samevapiClient.calls.get()method as theget_calltool.Documentation (
README.md):README.mdfile has been updated to include the newget_call_transcripttool in the "Supported Actions" section.