Skip to main content
Glama

List Interfaces

netbox_list_interfaces
Read-onlyIdempotent

List device interfaces from NetBox with pagination and filtering by device, name, type, MAC, VLAN, and more.

Instructions

List device interfaces (physical, virtual, LAG) from NetBox.

Supports pagination and filtering. Common patterns:

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

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

  • device_id: Numeric device id.

  • device: Device name.

  • name: Exact interface name.

  • name__ic: Interface name contains (case-insensitive).

  • type: Interface type slug, e.g. '1000base-t', '10gbase-x-sfpp', 'virtual', 'lag'.

  • enabled:

  • mgmt_only:

  • mac_address: Exact MAC (lowercase colon form).

  • mode: 802.1Q mode.

  • vlan_id: Tagged/untagged VLAN id match.

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).
modeNo802.1Q mode.
nameNoExact interface name.
typeNoInterface type slug, e.g. '1000base-t', '10gbase-x-sfpp', 'virtual', 'lag'.
limitNoMaximum number of items to return per page (1-1000, default 50).
deviceNoDevice name.
offsetNoNumber of items to skip for pagination. Use next_offset from a previous response.
enabledNo
vlan_idNoTagged/untagged VLAN id match.
name__icNoInterface name contains (case-insensitive).
device_idNoNumeric device id.
mgmt_onlyNo
mac_addressNoExact MAC (lowercase colon form).
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 (readOnly, idempotent, non-destructive), the description details pagination (limit, offset, auto-truncation, has_more, next_offset) and response formats. This adds significant 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, starting with purpose, then usage patterns, pagination details, filter lists, and return format. It is efficient and concise, with no wasted sentences.

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?

For a tool with 17 parameters and no output schema, the description covers all essential aspects: filters, pagination, response shape, and common use cases. It is comprehensive enough for an agent to use correctly.

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 88% schema coverage, the description adds value by providing example type slugs, explaining pagination parameters' behavior, and clarifying the response_format parameter. It does not fully document every parameter beyond the schema, but the added examples and context justify a 4.

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 device interfaces from NetBox, including physical, virtual, and LAG. It distinguishes from sibling netbox_get_interface by noting the lookup-by-id pattern, 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 Guidelines5/5

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

Explicit usage patterns are provided: discovery with no filters, lookup by id via alternative tool, and narrow scan with filters. This gives clear guidance on when to use this tool vs. alternatives.

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