Skip to main content
Glama

List Locations

netbox_list_locations
Read-onlyIdempotent

List locations like rooms, floors, and cages within a NetBox site. Filter by name, site, parent, or status and paginate results.

Instructions

List locations within a site (rooms, floors, cages) from NetBox.

Supports pagination and filtering. Common patterns:

  • Discovery: call with no filters to browse the first locations.

  • Lookup by id: use netbox_get_location instead when you already have an id.

  • Narrow scan: combine 'q' (fuzzy text) with resource-specific filters below.

Pagination:

  • 'limit' (max 1000, default 50) and 'offset'. Response includes 'has_more' and 'next_offset'.

  • Large list responses auto-truncate to keep under the character limit; keep calling with next_offset to continue.

Resource-specific filters:

  • name: Exact name.

  • slug: Exact slug.

  • site_id: Numeric site id.

  • parent_id: Parent location id (for nested locations).

  • status: Location status.

Universal filters:

  • q (string) Fuzzy text search across searchable fields.

  • tag (string[]) AND-filter by tag slugs.

  • created_after (date) ISO-8601 lower bound on 'created'.

  • created_before (date) ISO-8601 upper bound on 'created'.

Returns: Markdown summary (default) or JSON with shape: { total, count, offset, limit, items: [...], has_more, next_offset? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFuzzy full-text search across the object's searchable fields (name, description, etc.).
tagNoFilter to objects that have ALL of these tag slugs. Repeat for multiple tags (AND semantics in NetBox).
nameNoExact name.
slugNoExact slug.
limitNoMaximum number of items to return per page (1-1000, default 50).
offsetNoNumber of items to skip for pagination. Use next_offset from a previous response.
statusNoLocation status.
site_idNoNumeric site id.
parent_idNoParent location id (for nested locations).
created_afterNoISO-8601 date; only return objects created on or after this date (e.g. 2024-01-01).
created_beforeNoISO-8601 date; only return objects created on or before this date.
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate read-only, idempotent, non-destructive behavior. The description adds value by detailing pagination behavior (limit, offset, has_more, next_offset) and auto-truncation for large responses. This goes beyond what annotations provide, though it does not cover all edge cases like rate limits or authentication.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections for purpose, common patterns, pagination, filters, and return format. It is relatively long but each section serves a purpose. Minor redundancy in filter descriptions could be trimmed, but overall it is fairly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 12 parameters and no output schema, the description covers pagination, filtering, and return format (Markdown and JSON shapes). It explains how to iteratively retrieve large lists. This is quite complete, though it could mention default return format and how to interpret the JSON response fields more explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 12 parameters. The description enhances by grouping filters into resource-specific and universal, providing usage context like combining filters and examples. This adds moderate value beyond the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists locations within a site (rooms, floors, cages) and distinguishes from sibling tools like netbox_get_location for single record lookup by id. The verb 'list' and resource 'locations' are specific, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage patterns: discovery, lookup by id (recommending netbox_get_location), and narrow scan with filters. It also explains pagination usage. However, it does not explicitly mention when not to use this tool versus other list tools like netbox_list_sites, though the context is clear from the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZenixSolutions/netbox-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server