Skip to main content
Glama
Tafeen

Homebox MCP Server

by Tafeen

update_product_by_id

Update an existing product by specifying its ID and optionally modifying identity, location, identifiers, purchase details, metadata, or status.

Instructions

Update an existing product with grouped parameters.

    Args:
        item_id: UUID of the item to update (required)
        identity: Optional identity updates {"new_name": str, "description": str, "asset_id": str}
        location: Optional location change {"id": str} or {"name": str}
        identifiers: Optional manufacturing updates {"serial_number", "model_number", "manufacturer"}
        purchase: Optional purchase updates {"price": float, "seller": str, "date": str, "warranty_expires": str}
        metadata: Optional metadata updates {"notes": str, "quantity": int, "tag_ids": [str], "tag_names": [str], "custom_fields": [{}]}
        status: Optional flag updates {"archived": bool, "insured": bool, "lifetime_warranty": bool}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
item_idYes
identityNo
locationNo
metadataNo
purchaseNo
identifiersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains parameter groups but does not disclose side effects, permission requirements, or behavior on missing products. It is moderately transparent.

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 using a docstring format with clear 'Args' listing. It is fairly concise, though could be slightly shorter by avoiding repetition of 'Optional' in every bullet.

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 the presence of an output schema (not detailed here), the description adequately covers the input parameters. It is sufficient for the tool's complexity, though it could mention potential errors or prerequisites.

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 0% schema description coverage, the description adds significant meaning by detailing each parameter group (e.g., identity, location). It compensates for the schema's lack of descriptions, though some details could be more explicit.

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 purpose: 'Update an existing product with grouped parameters.' It uses a specific verb ('update') and resource ('product'), and distinguishes from sibling tools like 'add_product' and 'delete_product_by_id'.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It implicitly suggests it's for updating existing products, but lacks conditions or exclusions.

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/Tafeen/homebox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server