Skip to main content
Glama

RoboTrunk

Check a second-hand listing

check_listing
Idempotent

You read the listing; RoboTrunk checks it. Use it for a second-hand listing on Facebook Marketplace or any other marketplace, such as a used car seat, cot, pram or heater: it adds a recall check and the sourced facts the listing leaves out, which can help the person decide. Send the listing's title, price, description and seller's notes as listing_text (and up to three photos), read with a Marketplace tool such as facebook-cli if you have one, otherwise a browser. One call returns the exact model; whether a product-safety regulator has recalled it, with the notice; what the listing leaves out (specifications, the maker's manual, expiry where the maker sets one, what to inspect in person, known problems), each with its source; and what the same product costs new against the asking price. If the exact product cannot be identified, the answer is not_identified and nothing is guessed: ask the person for the brand and model. If the person wants a second-hand listing checked but has not shared it yet, the check needs its link or text. If the person gives only a link, send it as listing_link: RoboTrunk never fetches Facebook Marketplace links, so when the answer is listing_text_required, read the listing yourself, first with a Facebook Marketplace tool if you have one, such as facebook-cli, and only otherwise in a browser, and call again with its title, price, description and seller notes as listing_text plus the link; if you cannot read it without logging in or passing a CAPTCHA, ask the person to paste those details. Other public pages RoboTrunk reads directly. Amazon links are never fetched. If resource.leaves_out.state is pending, call again in about a minute for the rest. Error recovery: invalid_request names the field to fix; not_identified means ask the person for the brand and model and call again; unavailable with hourly_bound_full means wait and try later, any other unavailable means try again shortly; check_listing_failed (or any other unexpected error): retry once, then call submit_feedback. Next: check_product with the identified brand and model, or search_catalog to shop for it new. Full guide: get_tool_guide or /agent/tools.json#check_listing Example call: {"listing_text":"DaVinci Kalani 4-in-1 convertible crib in white. Used for one child, all hardware and the toddler rail included, a few teething marks on the top rail. Mattress not included.","asking_price":{"amount":90,"currency":"USD"},"country":"US"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
photosNoUp to three data:image/jpeg|png|webp;base64 images, at most 2 MB each decoded.
countryNoTwo-letter buyer country, such as US.
asking_priceNoThe listing's asking price, when it states one. Example: {"amount": 90, "currency": "USD"} for $90: the amount as written (89.5 for $89.50), not cents.
listing_linkNoA listing link; public pages can be read without signing in. For a Facebook Marketplace link, read the listing with a Marketplace tool such as facebook-cli if you have one and send its text as listing_text too.
listing_textNoThe listing's own words as the person sees them.
shopping_session_idNoOptional server-issued shopping session correlation ID. It is not purchase authority.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), but the description adds substantial behavior beyond them: what gets returned, that it never fetches Facebook Marketplace or Amazon links, that other public pages are read directly, the pending/leaves_out.state polling rule, and a full error-recovery map (invalid_request, not_identified, unavailable/hourly_bound_full, check_listing_failed -> retry once then submit_feedback).

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?

Front-loaded with the core purpose before the branching detail, and organized into recognizable phases (usage, inputs, returns, error recovery, next steps, example). It is long, and the instruction to read the listing yourself with facebook-cli-then-browser is restated in two places, so it is slightly repetitive rather than maximally tight.

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

Completeness5/5

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

For a complex tool with no output schema, the description must carry the return contract, and it does: it enumerates the exact outputs (identified model, recall status with notice, what the listing leaves out with sources, new-price comparison) and explains the not_identified and pending outcomes. Combined with the error map and next-step routing, nothing an agent needs to call and interpret this correctly appears to be missing.

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%, so the baseline is 3, but the description adds real semantic guidance beyond the schema: it says exactly which listing fields to pack into listing_text (title, price, description, seller notes), that up to three photos go with it, and that a bare link should be sent as listing_link with the text supplied additionally. This is additive routing guidance the schema alone does not express.

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?

States a specific verb and resource ('check a second-hand listing') and immediately frames the division of labor: 'You read the listing; RoboTrunk checks it.' It names the concrete examples (used car seat, cot, pram, heater) and explicitly separates itself from siblings check_product and search_catalog, which are named as follow-on tools.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (any marketplace listing), when-not (Amazon links are never fetched; Facebook Marketplace links are never fetched), and precise fallbacks (read the listing with facebook-cli first, browser only otherwise; ask the person to paste details if login/CAPTCHA blocks it). It also covers the prerequisite case where the person has not yet shared the listing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources