fix: return full API response from get_call including messages/transcript #12
Conversation
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
…ript The get_call tool was only returning a subset of fields from the Vapi API. This change updates transformCallOutput to pass through the complete API response, including: - messages (full transcript with role, content, timestamps) - transcript (plain text transcript) - recordingUrl and stereoRecordingUrl - cost and costBreakdown - analysis and artifact data - Additional call metadata The CallOutputSchema has been updated to document these fields while using passthrough() to allow any additional fields from the API. Fixes: PRISM-5 Co-Authored-By: Claude <[email protected]>
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.
Summary
get_calltool to return the complete Vapi API response instead of filtering fieldsmessagesarray (containing the full transcript with role, content, timestamps) is now includedtranscript,recordingUrl,stereoRecordingUrl,cost,costBreakdown,analysis,artifact, and moreProblem
The
get_callMCP tool was only returning a subset of fields:id,createdAt,updatedAt,status,endedReason,assistantId,phoneNumberId,customer,scheduledAtThe Vapi REST API at
GET /call/{id}returns the complete call object including themessagesarray (transcript), but the MCP wrapper'stransformCallOutputfunction was stripping this data.Solution
Updated
transformCallOutputin/src/transformers/index.tsto spread the entire call object instead of selecting specific fields. TheCallOutputSchemain/src/schemas/index.tshas been updated to document the newly exposed fields while using Zod'spassthrough()to allow any additional fields from the API.Changes
src/transformers/index.tstransformCallOutputto pass through full API responsesrc/schemas/index.tsCallOutputSchemawith message, transcript, recording, and cost fieldssrc/__tests__/transformers.test.tsTest plan
messages,transcript,recordingUrl,cost, andcostBreakdownare included in the outputLinear Issue
Fixes: PRISM-5
Generated with Claude Code