The BGP available from Meraki MX may not be what you're thinking it is. E.g. you can't hook up an MX to an Internet link and simply learn the Internet routing table (or a subset thereof, controlled by the eBGP peer).
Instead BGP is used only to exchange routes in and out of Meraki AutoVPN. It's basically used in the Data Centre, to allow the branch SD-WAN to let the DC know which sites / subnets are reached via a particular Hub MX. It also allows a new service to be deployed in the DC and made readily reachable by all the branches on the SD-WAN.
Of course, the fact that it performs peer monitoring and provides dynamic updates also offers other benefits, in terms of solution resilience. If you want to do very clever route manipulation, you are likely to need to implement this within the upstream eBGP routers, with which the Hub MXs are peering.
https://documentation.meraki.com/MX/Networks_and_Routing/BGP