Zebu Data - Local Business Leads

Each tool targets a distinct object: abort a run, inspect a run, read dataset rows, read a key-value record, and run the Yelp scraper. There is mild overlap between get-actor-run (run details/stats) and get-dataset-items (run output rows), but descriptions make the boundary clear enough.

Four tools follow a readable kebab-case verb_noun pattern (abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record). The fifth is a long vendor-prefixed, double-dash name (delicious_zebu--yelp-advanced-business-scraper-pay-per-result) that breaks the convention entirely.

Five tools is a reasonable size for an Actor-platform wrapper, but for a server framed as 'Local Business Leads' only one tool actually produces leads while four are generic platform plumbing. It feels slightly thin for the advertised domain.

Read paths exist for runs, datasets, and key-value stores, but there is no list operation (list runs, list datasets, list stores) and no general start-run tool beyond the single hardwired Yelp scraper. Agents can work around this if they already hold IDs, but discovery workflows are missing.