Bulk-fetch Compass listings by url or listing_id_sha
compass_bulk_getFetch up to 200 Compass listings in one call, with each result returning property details or an error. Timeouts and bridge issues are marked retryable, letting you batch large data pulls without losing track of failures.
Instructions
Fetch up to 200 Compass listings in a single call. Returns one structured row per input target (no side-by-side summary table — use compass_compare_properties for that). Each row is either { listing_id_sha, url, property } on success or { listing_id_sha, url, error } on failure — one bad target never fails the whole call. When the failure was a bridge timeout (after one retry) or an unreachable bridge (issue #73), the row also carries { status: "timeout" | "bridge_down", retryable: true } — that is NOT a missing listing, so retry it (a cold bridge usually succeeds on the second call) rather than concluding Compass has no record. Targets accept the same url / listing_id_sha shape as compass_get_property. Calls fan out concurrently. extracted_features is populated per row. The raw description is omitted by default — pass include_description: true to keep it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| targets | Yes | Up to 200 targets to fetch. For higher counts, batch into multiple calls. | |
| include_description | No | Include the raw `description` on each row. Defaults to `false` — `extracted_features` is always populated. |