Grabblist

update_item

DestructiveIdempotent

Edit fields on one or more saved items. Pass a single id or an array of ids for batch updates (same fields applied to all). For batch: attributes are REPLACED not merged, og:image fallback is skipped.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Item ID or array of item IDs to update
`tags`	No	Replace all tags with this list
`notes`	No	User or AI notes — personal comments, thoughts, comparisons
`title`	No	Item title
`images`	No	All image URLs — replaces the entire images array
`reason`	No	Why this change was made (shown to user in change history)
`status`	No	Decision status: considering, shortlisted, decided, bought, rejected
`category`	No	Item category
`quantity`	No	How many of this item
`image_url`	No	Main image URL
`item_type`	No	What kind of item this is
`attributes`	No	Merge into existing attributes
`description`	No	Item description (max 2000 chars)
`is_favorite`	No	Set true to favorite, false to unfavorite
`target_price`	No	What the user wants to pay — not the actual price, but the goal price

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 3, 2026
- addedInput schema / properties / attributes / additionalProperties
```
Added value: +{
+  "oneOf": [
+    {
+      "maxLength": 500,
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ]
+}
```
- addedInput schema / properties / image_url / format
```
Added value: +"uri"
```
- addedInput schema / properties / image_url / maxLength
```
Added value: +2000
```
- changedInput schema / properties / image_url / type
```
Previous value: -"object"New value: +"string"
```
- addedInput schema / properties / images / items / format
```
Added value: +"uri"
```
- addedInput schema / properties / images / items / maxLength
```
Added value: +2000
```
- changedInput schema / properties / images / items / type
```
Previous value: -"object"New value: +"string"
```
First observedAug 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description earns credit for disclosing batch-specific behavior beyond the annotations: attributes are REPLACED rather than merged, and the og:image fallback is skipped. It does not mention permissions or what happens to unspecified fields on a single update.

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?

Three short sentences, front-loaded with the core action, followed by the id contract and then the batch caveats. No filler and nothing that restates the schema.

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?

For a 15-parameter destructive mutation with no output schema and annotation coverage of the safety profile, the description supplies the critical batch semantics an agent could otherwise get wrong. It leaves gaps around permission requirements, single-item merge behavior, and update_price vs update_item routing.

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?

Schema coverage is 100% and the schema itself documents replacement semantics for tags and images, so baseline 3 applies. The description adds genuinely new parameter behavior by clarifying that attributes are REPLACED for batch calls while the schema description says 'Merge into existing attributes' — a distinction only the description supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Edit fields on one or more saved items') and immediately defines the single-vs-batch id contract, which separates it from update_collection and add_item. Sibling differentiation is implicit through 'saved items' rather than an explicit contrast, so it stops short of a 5.

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?

It tells the agent how to invoke it for one or many items, but gives no when-to-use guidance or exclusions. Notably, a sibling update_price exists and this tool accepts target_price, yet nothing says which one to prefer — the agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Grabblist tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?