Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

fanaticscollect_sold_items

Search Fanatics Collect sold items. Searches Fanatics Collect's sales-history archive -- every completed sale across every marketplace, not just what the live search index currently surfaces.

Instructions

Search Fanatics Collect sold items. Searches Fanatics Collect's sales-history archive -- every completed sale across every marketplace, not just what the live search index currently surfaces. A separate product from Search, reached from the "View all sold items" link on every marketplace search page. purchase_price is what the buyer paid in US dollars: for WEEKLY and PREMIER auction sales it includes the buyer's premium, so it is higher than the listing's final bid; for FIXED sales it equals the asking price. Credential-free public data from Fanatics Collect's own public sales-history API. See GetCategories for the accepted category, grading-service, eye-appeal-grade, and sort values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number, default 1
sortNoResult order. Default sold_date_desc.
titleNoFree-text search across item title
categoryNoItem category
max_yearNoMaximum card/item year, inclusive
min_yearNoMinimum card/item year, inclusive
per_pageNoResults per page, default 20, max 100
max_priceNoMaximum sold price, inclusive
min_priceNoMinimum sold price, inclusive
grading_serviceNoGrading/authentication service, including ungraded for raw items
eye_appeal_gradeNoEye-appeal grade

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does add real behavioral context: the coverage scope (every completed sale across every marketplace, including sales the live index no longer surfaces) and the semantics of purchase_price, including buyer's-premium inclusion for WEEKLY/PREMIER vs. asking price for FIXED. It does not describe pagination behavior, rate limits, or the shape of returned results, leaving some gaps for a no-annotation tool.

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-loads the core purpose and scope, then layers pricing semantics and a pointer to GetCategories; each sentence earns its place. It is somewhat dense and could shed one clause, but nothing is redundant.

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 an 11-parameter, no-annotation, no-output-schema tool, the description covers scope, data provenance (credential-free public sales-history API), and price meaning. With no output schema it could say more about what a sold-item record contains and how paging works, so a minor gap remains.

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 coverage is 100% and the enums for category, sort, grading_service, and eye_appeal_grade are already inline, so the schema does the heavy lifting; the description only points to GetCategories for the same value lists, adding little beyond it. The purchase_price explanation concerns a result field rather than an input parameter. Baseline 3 is appropriate.

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 ("Search Fanatics Collect sold items") and immediately scopes it against the sibling: sales-history archive of every completed sale, not just the live search index, and explicitly names Search as a separate product reached via the "View all sold items" link. An agent can distinguish this from fanaticscollect_search without opening either schema.

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?

Clearly frames when this tool applies versus the live-search sibling (archive of completed sales vs. currently surfaced listings) and routes the agent to GetCategories for accepted category, grading-service, eye-appeal-grade, and sort values. It does not state explicit exclusions or prerequisites (e.g., auth), so it falls just short of a 5.

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

Deploy Server

Other Tools