Create Rack
netbox_create_rackCreate a new rack in NetBox by specifying name, site, and optional attributes like role, location, dimensions, and status.
Instructions
Create a new rack in NetBox.
This adds a new row to NetBox. Ask before calling if the user wanted a dry-run.
Returns: Markdown summary of the newly created object (default) or JSON with the full NetBox response.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Rack name (required, unique within site+location). | |
| role | No | Rack role id. | |
| site | Yes | Site id (required). | |
| tags | No | Optional array of tag slugs to apply to the object. | |
| width | No | Rail-to-rail width in inches. | |
| serial | No | ||
| status | No | active | |
| tenant | No | Tenant id. | |
| weight | No | Rack weight. | |
| airflow | No | Airflow direction: front-to-rear, rear-to-front, left-to-right, right-to-left, side-to-rear, passive, mixed. | |
| comments | No | ||
| location | No | Location id. | |
| u_height | No | Height in rack units. | |
| asset_tag | No | ||
| rack_type | No | Rack type id (a predefined rack model). Alternative to setting form_factor/width/u_height individually. | |
| desc_units | No | Number rack units descending. | |
| max_weight | No | Maximum load capacity. | |
| outer_unit | No | ||
| description | No | Short description (distinct from the comments field). | |
| facility_id | No | Facility-assigned rack id. | |
| form_factor | No | Rack form factor: 2-post-frame, 4-post-frame, 4-post-cabinet, wall-frame, wall-frame-vertical, wall-cabinet, wall-cabinet-vertical. | |
| outer_depth | No | ||
| outer_width | No | ||
| weight_unit | No | ||
| outer_height | No | ||
| custom_fields | No | Optional object of custom-field slugs -> values. Only include fields defined on your NetBox instance. | |
| starting_unit | No | Unit number of the bottom position. | |
| mounting_depth | No | Maximum depth of a mounted device, in mm. | |
| response_format | No | Output format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls. | markdown |