Skip to main content
Glama

Shopgoodwill Sold Search

shopgoodwill_sold_search
Read-onlyIdempotent

Search closed ShopGoodwill auctions for realized sale prices, what items actually sold for at Goodwill online auctions. Price comps for used cameras, watches, jewelry, instruments, electronics and collectibles. Returns final hammer price, bid count and close date per lot; the archive reaches back about 90 days. Sourced from the shopgoodwill.com closed-auction search API.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "rolex",
      "days_back": 90
    },
    "name": "shopgoodwill_sold_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, starting at 1
queryYesSearch keywords, e.g. "rolex" or "fender stratocaster"
per_pageNoMax results to return, up to 40 (each source page holds 40 rows; use page to paginate)
days_backNoHow many days of closed auctions to search (default 30; archive holds ~90 days)
max_priceNoMaximum final price in USD
min_priceNoMinimum final price in USD
category_idNoOptional ShopGoodwill category id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavioral context beyond them: the archive depth (~90 days), the per-lot return fields (hammer price, bid count, close date), and the upstream source (the shopgoodwill.com closed-auction search API). What's missing is anything about result caps or pagination behavior at scale.

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 scope before the comps use case and return details. Minor redundancy in 'realized sale prices, what items actually sold for at Goodwill online auctions', where the second clause mostly restates the first, but it costs little and aids clarity.

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?

With no output schema, the description carries the return-value burden and does so by enumerating hammer price, bid count and close date per lot. All seven parameters are documented in the schema, and archive depth plus source API are disclosed. Only pagination/result-volume behavior and any rate limits are left unaddressed for what is otherwise a simple read-only search.

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 page, per_page, days_back, min/max_price and category_id are already fully documented in the schema itself. The description's note that the archive 'reaches back about 90 days' reinforces the days_back bound but is already stated in that parameter's description, so it adds little beyond structured data. 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 and resource ('Search closed ShopGoodwill auctions') plus the scope of the data ('realized sale prices', 'final hammer price'). The word 'closed' implicitly separates it from the live-listing sibling shopgoodwill_search, but the description never names that sibling or states the contrast explicitly, so the differentiation requires inference.

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

Usage Guidelines4/5

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

Provides a concrete use case – 'Price comps for used cameras, watches, jewelry, instruments, electronics and collectibles' – which tells the agent when this tool is the right pick (comparable sold prices rather than browsing inventory). It stops short of naming an alternative tool or stating when-not to use it, so it lands at clear-context-without-exclusions.

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.