Skip to main content
Glama

List Sites

netbox_list_sites
Read-onlyIdempotent

List physical sites from NetBox with filters for name, status, region, and full-text search, supporting paginated results.

Instructions

List physical sites (datacenters, offices, POPs) from NetBox.

Supports pagination and filtering. Common patterns:

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

  • Lookup by id: use netbox_get_site 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 site name.

  • slug: Exact site slug.

  • status: Site status.

  • region_id: Filter by numeric region id.

  • group_id: Filter by numeric site group id.

  • tenant_id: Filter by numeric tenant id.

  • asn: Filter by legacy ASN number.

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.).
asnNoFilter by legacy ASN number.
tagNoFilter to objects that have ALL of these tag slugs. Repeat for multiple tags (AND semantics in NetBox).
nameNoExact site name.
slugNoExact site 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.
statusNoSite status.
group_idNoFilter by numeric site group id.
region_idNoFilter by numeric region id.
tenant_idNoFilter by numeric tenant id.
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
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds critical behavioral details: pagination with limit/offset and auto-truncation, response shape (has_more, next_offset), and output format options (markdown vs JSON). No contradictions with annotations.

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: a concise opening, then sections for common patterns, pagination, filters, and returns. Every sentence adds value. Slightly lengthy due to comprehensive filter listing, but efficiently organized.

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

Completeness5/5

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

Given 14 parameters and no output schema, the description covers all parameters, pagination behavior, response formats, and common use patterns. It addresses edge cases like auto-truncation and provides clear guidance for chaining follow-up calls. Very complete for a list tool.

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?

With 100% schema coverage, baseline is 3. The description groups filters into resource-specific and universal categories, explains the fuzzy search 'q' and AND semantics for 'tag', and clarifies pagination parameters. This adds meaningful context beyond the schema.

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 it lists physical sites (datacenters, offices, POPs) from NetBox, distinguishing it from siblings like netbox_get_site which is for single ID lookup. The verb 'list' and resource 'sites' are specific, and common patterns help differentiate usage.

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 common patterns: discovery with no filters, lookup by id (recommends netbox_get_site instead), and narrow scan with filters. Pagination usage is explained. While not exhaustive on when not to use, it effectively guides the agent on typical scenarios.

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