Update Inventory Item
update_inventory_itemPatch one owned Inventory item, found by inventory_id or by nickname: what the user calls it ("MacBook", "work laptop"), matched to exactly one of their active items by nickname, name or model, so there is no need to look it up first; several matches are refused with the candidates and nothing changes. Fields you leave out are untouched. specs merge per key (null removes a key), so updating memory keeps storage. state records a new observation (observed_at, source, confidence) and never changes specs or notes; a key already observed more recently is kept. spec_template switches or clears (null) the template. A status like sold or donated moves it out of the active list; to archive, use archive_inventory_item. Never add device or account identifiers. ($0.10; API key required)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | What the user calls the item, e.g. "MacBook Pro 14 (2023)". | |
| tags | No | Replaces the tag list. | |
| brand | No | ||
| model | No | ||
| notes | No | Free text from the user. | |
| specs | No | Stable facts, by the template's field names (computer.v1: nickname, manufacturer, model_name, model_identifier, year, primary_uses, capability_tags, product_family, form_factor, chip, cpu, architecture, performance_cores, efficiency_cores, total_cores, threads, gpu, gpu_cores, gpu_memory_bytes, neural_engine_cores, memory_bytes, memory, storage_devices, display, ports). Merged per key on update; null removes a key; other keys are kept as written. Only what the user or the device says, never inferred from a model name. Never device or account identifiers. | |
| state | No | Changing facts, as one observation: observed_at (ISO, default now), source (e.g. user_reported, system_profiler), confidence (0-1), and values such as os { name, version, build }, available_storage_bytes, battery, security { sip, gatekeeper, filevault }, services { bluebubbles: { installed_version, running, configured, blockers, checked_at } }. Merged per key; a key observed more recently is kept. Never changes specs or notes. Never device or account identifiers. | |
| status | No | Default owned. To archive, use archive_inventory_item. | |
| subtype | No | Specific kind: laptop, sweatshirt, guitar. Alias: item_type. | |
| category | No | electronics | instruments | clothing | shoes | bags | accessories | jewelry | watches | collectibles | sports | health | home | tools | vehicles | furniture | other. Computers, phones and cameras are electronics; synths are instruments. Defaults to the spec_template's category, else other. | |
| currency | No | ISO 4217, e.g. USD, SGD. Default USD. | |
| location | No | Where it is kept. | |
| nickname | No | In place of inventory_id: what the user calls the item ("MacBook", "work laptop"), matched to exactly one of their active items by nickname, name or model. Several matches are refused with the candidates. To rename it, set specs.nickname. | |
| condition | No | ||
| item_type | No | Alias for subtype (the stored column). | |
| request_id | No | Client idempotency key (retries return original result). | |
| inventory_id | No | The item id from add_inventory_item, get_inventory or search_inventory. | |
| acquired_date | No | YYYY-MM-DD it came into the user's life (gift, inheritance). add_inventory_item also stores it as purchase_date when none is given. | |
| acquired_from | No | Shop or person it came from. | |
| current_value | No | Alias for estimated_value (the stored column). | |
| purchase_date | No | YYYY-MM-DD | |
| spec_template | No | Which typed fields specs uses. Templates are listed in docs/MCP_LIFE_GRAPH.md. null (update) clears it. | |
| purchase_price | No | ||
| estimated_value | No | What it is worth now. Alias: current_value. | |
| idempotency_key | No | Alias for request_id. | |
| acquisition_type | No | purchase | gift | inheritance | … | |
| reference_number | No | Manufacturer reference or model number (e.g. a watch reference). | |
| subtype_confidence | No | 0-1, when the subtype is a guess. | |
| specs_schema_version | No | Layout of specs and state. Only 1 (the default). |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| item | No | Inventory item record. With specs: spec_template, specs, state (a timestamped snapshot), state_freshness and capability_summary. | |
| account | No | The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer. | |
| changed | No | ||
| message | No | ||
| provenance | No | Which connector wrote the record and which connected Dayze account received it. | |
| state_note | No | ||
| inventory_id | No | ||
| resolved_from | No | PHI-448: present when nickname found the item: the nickname sent and matched_on (nickname, name or model). | |
| changed_fields | No | Columns set, and the specs / state keys written. | |
| idempotent_replay | No | ||
| state_not_applied | No |