Skip to main content
Glama

List Vlans

netbox_list_vlans
Read-onlyIdempotent

Retrieve and filter layer-2 VLANs from NetBox using criteria like VID, name, status, site, or group. Paginated results with fuzzy search.

Instructions

List layer-2 VLANs from NetBox.

Supports pagination and filtering. Common patterns:

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

  • Lookup by id: use netbox_get_vlan 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:

  • vid: Exact VLAN id (1-4094).

  • name:

  • name__ic: Name contains (case-insensitive).

  • status:

  • site_id:

  • group_id: VLAN group id.

  • role_id:

  • tenant_id:

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).
vidNoExact VLAN id (1-4094).
nameNo
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.
statusNo
role_idNo
site_idNo
group_idNoVLAN group id.
name__icNoName contains (case-insensitive).
tenant_idNo
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?

Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds pagination details (limit, offset, has_more, next_offset), auto-truncation for large lists, and return format options, providing full behavioral context.

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

Conciseness5/5

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

The description is well-organized into sections (intro, common patterns, pagination, filters, returns). Every sentence adds value, no redundancy. Front-loaded with key information.

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 15 parameters and no output schema, the description covers purpose, usage patterns, pagination, filtering, and return format. Includes important details like auto-truncation and response_format parameter. 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?

Schema coverage is 67%. The description groups parameters into 'Resource-specific filters' and 'Universal filters', adding structure. It adds context for pagination and response format. However, several parameters (name, status, role_id, site_id, tenant_id) lack schema descriptions and the description only lists them without further detail.

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 'List layer-2 VLANs from NetBox' with specific verb and resource. It distinguishes from siblings like 'netbox_get_vlan' by recommending the get tool when an ID is already known.

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

Usage Guidelines5/5

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

The description provides explicit common patterns: discovery (no filters), lookup by id (recommends netbox_get_vlan), and narrow scan (combine filters). It also explains pagination and when to use the json format for chaining.

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