Grabblist

add_item

Save an item to the user's Grabblist. Creates a static snapshot — Grabblist does not monitor prices or auto-update data. Only include fields with values available from the source. Price is optional: omit it for videos and other things without a price. If no image is provided, the server attempts to fetch og:image automatically.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Direct public HTTP(S) page URL.
`tags`	No	Tags for categorization
`image`	No	Main image URL. Server auto-fetches og:image if not provided.
`price`	No	Price as a number (e.g. 99.99), taken from the page. Omit when the item has no price (videos, free content).
`title`	Yes	Exact title from the page
`images`	No	All image URLs found on the page
`reason`	No	Why this change was made (shown to user in change history)
`category`	No	Category — pick the best match
`currency`	No	Currency code of the price: USD, NZD, AUD, EUR, GBP, etc. Omit when there is no price.
`location`	No	Seller location or pickup location
`platform`	Yes	Site domain name without TLD: amazon.com→"amazon", ebay.co.nz→"ebay", kiwiquads.co.nz→"kiwiquads"
`quantity`	No	How many of this item
`condition`	No	Condition if applicable: New, Used, Refurbished, Used - Like New, Used - Good, Used - Fair
`item_type`	No	What kind of item: product (buy), rental (Airbnb), service (cleaning), course (Udemy), listing (classified), event (ticket), video (YouTube, Twitch, TikTok, Vimeo…). If omitted, the server infers it from the platform (video sites → video, otherwise product).
`posted_at`	No	When the listing was originally posted (ISO 8601)
`attributes`	No	Specs/details as key-value pairs
`description`	No	Description from the page (max 2000 chars)
`seller_name`	No	Seller or store name
`seller_rating`	No	Seller rating 0-5
`original_price`	No	Original price before discount (if on sale)
`seller_reviews`	No	Number of seller reviews

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 3, 2026

changedInput schema / properties / currency / description

Previous value: -"Currency code: USD, NZD, AUD, EUR, GBP, etc."New value: +"Currency code of the price: USD, NZD, AUD, EUR, GBP, etc. Omit when there is no price."

changedInput schema / properties / item_type / description

Previous value: -"What kind of item: product (buy), rental (Airbnb), service (cleaning), course (Udemy), listing (classified), event (ticket). Default: product."New value: +"What kind of item: product (buy), rental (Airbnb), service (cleaning), course (Udemy), listing (classified), event (ticket), video (YouTube, Twitch, TikTok, Vimeo…). If omitted, the server infers it from the platform (video sites → video, otherwise product)."

changedInput schema / properties / item_type / enum

Previous value: -[
-  "product",
-  "rental",
-  "service",
-  "course",
-  "listing",
-  "event",
-  "other"
-]New value: +[
+  "product",
+  "rental",
+  "service",
+  "course",
+  "listing",
+  "event",
+  "video",
+  "other"
+]

changedInput schema / properties / price / description

Previous value: -"Price as number (e.g. 99.99) — REQUIRED, extract from page"New value: +"Price as a number (e.g. 99.99), taken from the page. Omit when the item has no price (videos, free content)."

changedInput schema / required

Previous value: -[
-  "url",
-  "title",
-  "price",
-  "currency",
-  "platform"
-]New value: +[
+  "url",
+  "title",
+  "platform"
+]

Changed10 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 / format
```
Added value: +"uri"
```
- addedInput schema / properties / image / maxLength
```
Added value: +2000
```
- changedInput schema / properties / image / 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"
```
- addedInput schema / properties / url / format
```
Added value: +"uri"
```
- addedInput schema / properties / url / maxLength
```
Added value: +2000
```
- changedInput schema / properties / url / type
```
Previous value: -"object"New value: +"string"
```
First observedAug 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Adds real behavioral context beyond the annotations: the save is a static snapshot with no price monitoring or auto-updating, and the server auto-fetches og:image when none is supplied. This is exactly the kind of consequence disclosure annotations can't carry. It omits duplicate/idempotency behavior, which matters given idempotentHint=false, so it is not a 5.

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?

Four short sentences, front-loaded with the core action and the snapshot caveat before the field-level advice. Efficient, though the price and image notes duplicate the schema and could have been dropped.

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?

For a 21-parameter mutation with no output schema, the description covers the essential snapshot semantics and the image fallback, but says nothing about what is returned, whether duplicates create new items (idempotentHint=false), or auth requirements. Adequate but with clear gaps.

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 100%, so the schema already documents every parameter, and the description largely repeats it — the price-optional and image auto-fetch notes are already present in the schema property descriptions. Baseline 3 is appropriate.

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+resource: 'Save an item to the user's Grabblist.' An agent knows this is a create operation on a single item. It does not, however, distinguish itself from close siblings like add_to_collection or update_item, 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?

Gives conditional guidance about parameters ('omit price for videos', 'only include fields with values available from the source') but says nothing about when to choose add_item over add_to_collection or how it relates to update_item. Usage is implied rather than contextualized against alternatives.

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?