Google Flights round-trip search
Input
origin requiredOrigin city or airport, free text or IATA (e.g. 'Paris' or 'CDG').
depart_date requiredOutbound date, ISO YYYY-MM-DD.
destination requiredDestination city or airport, free text or IATA (e.g. 'Tokyo' or 'NRT').
return_date requiredReturn date, ISO YYYY-MM-DD (must be after depart_date).
max optionalMax outbound options to return. Price-less rows are skipped so fewer may come back.
Default: 10Output
flights requirednoResults requiredTrue when Google Flights could not resolve the route (lands on the empty search splash).
Search Google
Run a Google search and return the page's organic result cards (title, url, site, byline, meta, snippet), with redirect wrappers already cleaned from urls. Runs with your injected Google cookies (loggedIn:true), so results are personalized to your account/IP. Supports full Google query syntax: site:, quoted "exact phrases", OR, -exclude, intitle:. Quoted phrases return a smaller, more precise set; dropping quotes broadens recall with some near-miss results mixed in. Use site: to scope a domain/path, e.g. site:www.linkedin.com/in. Each call returns one results page (up to ~10 organic cards, no per-call count option). Use `page` (0-based) to move through further pages, mirroring the search results pager. Pages are reproducible on the same account/IP and are largely non-overlapping (occasional overlap of one result at page boundaries), so different pages can be fetched concurrently and unioned — always dedupe by canonical url. Narrow queries return the same results in the same order across replays on one account/IP; very broad, high-volume queries may reorder between runs. For broader coverage, fetch multiple pages concurrently and/or split the query itself — vary the site: path, phrases/OR-terms, or use `freshness` for disjoint date-bounded windows. Always dedupe by url.
Search Google Maps places
Search Google Maps for places matching a query, optionally near a location. Returns n, captured, and records with name, address, phone, website, rating, category, lat, lng, placeId, and placeUrl. placeId is the join key for get_place and get_place_reviews; rating, category, lat and lng can be null.
Search Gmail
Search the signed-in Gmail with the native query syntax (from:, to:, subject:, has:attachment, after:/before:, labels…) and return matching threads: threadId (feed it to get_thread / reply_to_email), sender, senderEmail, subject, snippet, date, unread, starred, hasAttachment. Results are threads rather than individual messages, which is Gmail's own search granularity, and only the first page of results is returned (up to 50).