List Rack Storage Items
hudu_list_rack_storage_itemsList rack storage items in Hudu using filters for side, status, asset ID, unit positions, role, or timestamps. Returns every matching mounted equipment record with its rack placement details.
Instructions
List rack storage items in Hudu. A rack storage item is one thing mounted in a rack: it points at the Hudu asset it represents, occupies the units from start_unit to end_unit on one side of the rack, and carries its own power figures. The rack itself is a rack storage — use the hudu_*_rack_storage tools for the cabinet.
Read this before answering a question about a specific rack: the API documents no way to list the items in one. The item schema has no rack field, and none of the filters scope to a rack — rack_storage_role_id filters by role, which is a classification, not the cabinet. The documented filters are role, asset, start_unit, end_unit, status, side and the two timestamps, all of them instance-wide. If you are asked what is in rack 12, say this API does not expose it rather than presenting an unscoped list as that rack's contents. It is worth reading one record with hudu_get_rack_storage_item to see whether your Hudu version returns a rack reference the published schema omits, but do not assume one is there.
To go the other way — from a device to where it is racked — filter by asset_id, which is the one filter that ties an item to something you can identify elsewhere in Hudu.
This endpoint documents neither page nor page_size, so this tool sends neither and Hudu answers with everything matching in one response. The envelope reports page_was_full: false and next_page: null accordingly — there is no second page to ask for, and what you get back is the complete set for the filters given. If the result comes back marked truncated, that is this server trimming the response to fit its output budget, not the end of the data; narrow the filters or use fields to see the rest.
Returns an object with items plus pagination facts. Note that the Hudu API returns no total count for any collection, so page_was_full is the only honest signal that more records exist — read pagination_note before concluding a list is complete.
Operation class: Read.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| side | No | Return only items mounted on this face: the filter documents the strings "Front" and "Rear". Note that the create and update body documents the same field as an integer, so the value you filter with is not the value you write. | |
| fields | No | Return only these top-level fields on each record. Use it to keep large lists small — e.g. ["id","name","company_id"]. Unknown field names are ignored. | |
| status | No | Return only items with this integer status. No legal values are documented. | |
| asset_id | No | Return only items representing this Hudu asset, by numeric asset id from hudu_list_assets. This is how you find where a known device is racked. | |
| end_unit | No | Return only items whose end unit equals this value exactly. | |
| created_at | No | ISO-8601 range as "start,end". Either side may be omitted — "2026-01-01T00:00:00Z," means everything since that moment, ",2026-01-01T00:00:00Z" everything before it. A bare timestamp with no comma matches that exact moment. | |
| start_unit | No | Return only items whose start unit equals this value exactly. | |
| updated_at | No | ISO-8601 range as "start,end". Either side may be omitted — "2026-01-01T00:00:00Z," means everything since that moment, ",2026-01-01T00:00:00Z" everything before it. A bare timestamp with no comma matches that exact moment. | |
| response_format | No | Output shape. 'json' (default) is compact and machine-readable; 'markdown' is easier for a person to read but larger. | json |
| rack_storage_role_id | No | Return only items holding this rack storage role. A role is a classification of the mounted item, not the rack it is in — this does not list the contents of a rack. |