Skip to main content
Glama

Update Location

netbox_update_location
DestructiveIdempotent

Update an existing location in NetBox with PATCH semantics: provide the location ID and only the fields to modify. Unchanged fields are preserved. Returns a markdown summary or full JSON.

Instructions

Update an existing location in NetBox (PATCH semantics — only provided fields are changed).

Supply the numeric 'id' and only the fields you want to change. Omitting a field leaves it unchanged.

Returns: Markdown summary of the updated object (default) or JSON with the full NetBox response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric id of the location to update.
nameNo
siteNo
slugNo
tagsNoOptional array of tag slugs to apply to the object.
parentNo
statusNo
tenantNo
commentsNo
facilityNo
descriptionNo
custom_fieldsNoOptional object of custom-field slugs -> values. Only include fields defined on your NetBox instance.
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (full structured payload). Use 'json' when chaining follow-up tool calls.markdown
Behavior1/5

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

The description claims 'only provided fields are changed' (non-destructive PATCH), but the annotations have destructiveHint: true, indicating potential data destruction. This contradiction means the description undermines behavioral transparency. Score 1 per rubric for contradiction.

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?

Extremely concise: two sentences plus a returns line, front-loaded with purpose and PATCH semantics. Every sentence adds value without waste.

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

Completeness3/5

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

Minimally adequate: describes update behavior and output format, but given 13 parameters, low schema coverage, and no output schema, more detail on typical use cases or return structure would improve completeness.

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

Parameters2/5

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

Only 31% of parameters have schema descriptions, and the description adds no additional parameter semantics beyond the schema. Key fields like 'parent', 'site', 'status' are not explained, leaving the agent without guidance for proper usage.

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 action ('Update an existing location') and the resource ('location'). It specifies PATCH semantics and mentions the required 'id', distinguishing it from creation tools like netbox_create_location.

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

Usage Guidelines3/5

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

Provides basic guidance to supply the numeric 'id' and only desired fields, but lacks explicit when-to-use or when-not-to-use context compared to sibling tools (e.g., create, delete).

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