Rides

Coming soon

Rides tools aren't available on Careem MCP yet, and they aren't in the Local Sandbox either. Their contracts are published below so you can plan your integration.

Tool	Purpose	Key parameters
`search_locations`	Search locations / POIs	`query`, `latitude`, `longitude`
`search_locations_batch`	Try several term variations for one unclear location in a single call	`locationTerms[]` (up to 5 variations — spellings, abbreviations, nearby landmarks), `latitude`, `longitude`
`request_ride`	Get ride products + prices for a route (returns `context_blob`)	`pickup`, `dropoff` (text or coords), `latitude`, `longitude` (user's current coords), optional structured `pickup_location`/`dropoff_location`, `selectedProductId`
`request_scheduled_ride`	Same, for a future pickup	+ `pickupTime` (RFC3339, future)
`create_ride` ⚠️	Book the ride	`selectedProduct`, `context_blob` (verbatim from `request_ride`, short-lived), `pickup_latitude`, `pickup_longitude`, `dropoff_latitude`, `dropoff_longitude` (must match the pickup/dropoff used to get `context_blob`), optional `payment_type` (cash \| card \| wallet)
`get_ride_cancellation_reasons`	List cancellation reasons	`rideId`
`get_ride_cancellation_attributes`	Cancellation fee details (returns `pricingId`)	`rideId`, optional `cancellationReasonId`
`cancel_ride` ⚠️	Cancel a ride	`rideId`, `pricingId` (from attributes), optional `answer` (reason picked from `get_ride_cancellation_reasons`)
`apply_promotion_code` ⚠️	Apply a promo code to the account	`code`, `latitude`, `longitude`
`get_ride_schedule_policy`	Get scheduling policies for rides	`latitude`, `longitude`

tip

The context_blob returned by request_ride must be passed verbatim to create_ride and is short-lived — book promptly after the user picks a product.

Flow

Resolve pickup/dropoff with search_locations (or search_locations_batch if a single query for an unclear location doesn't return a good match).
Get products/prices with request_ride (or request_scheduled_ride for a future pickup) — optionally check get_ride_schedule_policy first for scheduling constraints, and apply_promotion_code if the user has a code.
Book with create_ride, passing context_blob verbatim.
Track with get_activities / track_activity (activity_type=ride).
To cancel: get_ride_cancellation_reasons → get_ride_cancellation_attributes (for pricingId) → cancel_ride.

See the Book a ride journey for the full sequence.