Zebu Data - Zillow Real Estate Data

Each tool maps to a clearly distinct resource and action: aborting an Actor run, getting Actor run details, reading dataset items, and reading a key-value store record. There is minimal overlap, and an agent can select the right tool based on resource type and verb.

All names use lowercase hyphenated verb-resource conventions: abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record. The pattern is predictable and easy to scan.

Four tools is not excessive, but for a server branded around Zillow real estate data it feels thin because the surface only covers generic Actor-run/result operations. The count is reasonable for a focused Apify result-retrieval subset, but not for the stated domain.

The set lacks a way to start an Actor run, list actors/datasets/key-value stores, or query Zillow properties directly. It can inspect and abort runs and read outputs, but there is a critical gap at the beginning of the data-retrieval lifecycle.