fix: expose phone number provider and add outbound call guidance#15
Closed
vapi-tasker[bot] wants to merge 1 commit intomainfrom
Closed
fix: expose phone number provider and add outbound call guidance#15vapi-tasker[bot] wants to merge 1 commit intomainfrom
vapi-tasker[bot] wants to merge 1 commit intomainfrom
Conversation
Customers using create_call with a Vapi-provisioned phone number get a cryptic transport error because Vapi numbers are inbound-only. This change surfaces the provider field so MCP clients can identify which numbers support outbound dialing, and updates tool descriptions to clearly communicate the Twilio/Vonage requirement. Changes: - Add provider field to PhoneNumberOutputSchema and transformer - Update create_call tool description with outbound requirements - Update CallInputSchema.phoneNumberId with provider guidance - Add 6 unit tests covering all three fixes Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
Fixes the cryptic
call.start.error-get-transport — Vapi Numbers Can't Dial Outbound Yeterror that MCP users encounter when usingcreate_callwith a Vapi-provisioned phone number.Root cause: The MCP server did not expose the phone number
providerfield, so clients had no way to determine which numbers support outbound dialing. Additionally, tool descriptions gave no guidance about the Twilio/Vonage requirement for outbound calls.Changes:
providerfield toPhoneNumberOutputSchemaandtransformPhoneNumberOutputso MCP clients can see whether a number isvapi(inbound-only),twilio, orvonage(outbound-capable)create_calltool description to clearly state that outbound calls require a Twilio or Vonage imported phone numberCallInputSchema.phoneNumberIddescription with guidance about which phone numbers work for outboundTest plan
providerfield"unknown"when provider is missingphoneNumberIddescription mentions Twilio, Vonage, and outboundtsc --noEmitLinear issue
PRO-1050
Generated with Claude Code