Zebu Data - Amazon & eBay Product Data

Each tool targets a distinct resource/action: abort a run, inspect a run, read dataset items, read a key-value record. The two 'actor-run' tools differ clearly (abort vs. get), and the two read tools operate on different storage types (dataset vs. key-value store). No plausible confusion between any pair.

All four names follow a consistent kebab-case verb-resource pattern (abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record). The convention is uniform and predictable, with 'get-*' grouping the retrieval operations.

Four tools is thin for a server framed around Amazon & eBay product data scraping, since all four are generic Apify storage primitives. Each tool arguably earns its place, but the surface feels under-built for the advertised purpose.

There is no tool to start/run an Actor, list Actors, or list datasets/stores, so an agent cannot initiate the data-extraction workflow the server implies. Only abort plus read operations are exposed, leaving a significant lifecycle gap.