Zebu Data - TripAdvisor Travel Data

The four infrastructure tools (abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record) each target a clearly different Apify resource, so misselection is unlikely. The one weak spot is the oddly slugged 'delicious_zebu--tripadvisor-review-collector', whose name does not signal that it both starts a run and returns results, making its relationship to get-actor-run less obvious.

Four tools follow a clean kebab-case verb-noun pattern (abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record). The fifth deviates entirely, using a slugified actor ID with a double-dash separator instead of a verb, which breaks the pattern.

Five tools is a reasonable size, but four of them are generic platform plumbing and only one actually touches the advertised TripAdvisor domain. For a server billed as 'TripAdvisor Travel Data' with five review categories and rich filters, the surface feels thin.

The core pipeline works: run the review collector, poll with get-actor-run, then pull rows via get-dataset-items. However, there is no way to start a run with explicit parameters, list existing runs/datasets, or inspect dataset metadata/schema, leaving agents with dead ends outside the single happy path.