Skip to main content
Glama

List Ip_addresses

netbox_list_ip_addresses
Read-onlyIdempotent

List and filter IP addresses from NetBox using address, parent CIDR, status, role, and pagination support.

Instructions

List individual IP addresses from NetBox.

Supports pagination and filtering. Common patterns:

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

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

  • address: Exact address with mask, e.g. '10.0.0.5/32'.

  • parent: Return addresses within this CIDR, e.g. '10.0.0.0/24'.

  • family:

  • status:

  • role:

  • dns_name:

  • vrf_id:

  • tenant_id:

  • assigned_to_interface:

  • interface_id: Restrict to one device interface.

  • vminterface_id: Restrict to one VM interface.

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).
roleNo
limitNoMaximum number of items to return per page (1-1000, default 50).
familyNo
offsetNoNumber of items to skip for pagination. Use next_offset from a previous response.
parentNoReturn addresses within this CIDR, e.g. '10.0.0.0/24'.
statusNo
vrf_idNo
addressNoExact address with mask, e.g. '10.0.0.5/32'.
dns_nameNo
tenant_idNo
interface_idNoRestrict to one device interface.
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.
vminterface_idNoRestrict to one VM interface.
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
assigned_to_interfaceNo
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds value by detailing pagination (limit, offset, has_more, next_offset, auto-truncation) and return format options. 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-organized with sections for common patterns, pagination, and filters. It front-loads the main purpose. Some filter entries are empty, making it slightly longer than necessary, but overall clear and structured.

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 18 parameters and no output schema, the description covers pagination, response format, and most filter parameters. Missing descriptions for a few parameters are partially compensated by schema enums. It explains common patterns and return options well.

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

Parameters3/5

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

Schema description coverage is 61%, so the description must add context. It lists resource-specific filters but leaves some (family, status, role, etc.) with empty descriptions. However, schema enums cover most of these. The description adds value for pagination and common patterns. Overall adequate but not thorough.

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 individual IP addresses from NetBox', a specific verb and resource. It differentiates from netbox_get_ip_address by advising to use that tool when an ID is known. The common patterns section further clarifies 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 when-to-use guidance (discovery, narrow scan) and when-not (lookup by id, recommending netbox_get_ip_address). It does not cover alternatives like netbox_list_prefixes, but the cross-referencing is sufficient for the primary sibling.

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