User
| Tool | Purpose | Key parameters |
|---|---|---|
user_info | Profile + saved bookmarks (Home/Work) + routines | optional coords, service_area_id |
get_activities | Activities across verticals | activity_status? (past | upcoming | ongoing), activity_type? (ride | food | groceries | shops | delivery), next_cursor? (paginate past activities) |
track_activity | Live tracking of one ongoing activity | activity_type (ride | food | groceries | shops), reference_id |
Usage
Pass activity_type (ride | food | groceries | shops | delivery) to scope to one vertical — omit it for a cross-vertical view. activity_status takes past, upcoming, or ongoing (omit for all three). Results are paginated at up to 35 past activities per call; keep passing next_cursor to page further back (up to 3 calls / 105 activities). For live status, call get_activities(activity_status=ongoing) first, then track_activity with that entry's activity_type and reference_id for the current ETA.
tip
Use user_info to resolve "home" and "work" into saved addresses, and get_activities(past) to prefer the user's known favourites over cold search.
Flow
- Call
user_infoup front to resolve saved addresses and getservice_area_id/city_idfor other tools. - Use
get_activitiesto list past/upcoming/ongoing orders across verticals (page through past ones withnext_cursor), thentrack_activitywith an activity'sreference_idfor live tracking of an ongoing one.