Assuming this is the "InsertMedia" action found in the VirtualMedia resource, the simplistic type of request would only require the Image parameter; specifying the protocol type via the TransferProtocolType parameter is only necessary when there is no scheme in the associated image URI. You clearly have HTTPS called out in the image URI, so this appears to be a bug with the implementation you're using. I'd recommend reaching out to the vendor's support.
In the meantime, you could try adding the "TransferProtocolType" parameter with the value "HTTPS" to see if that works around the issue, but again, this should not be necessary to do. The other thing to note is "VmmControlType" is not defined in the action, so I would remove that parameter.