Open
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>
Author
|
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? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.