Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticscollect_search

Search Fanatics Collect marketplace listings across auctions and Buy Now by keyword, category, grading service, price, year, grade, and status. Sort and filter results to narrow broad queries.

Instructions

Search Fanatics Collect listings. Searches Fanatics Collect's full marketplace -- weekly auctions, premier auctions, and the fixed-price "Buy Now" marketplace -- by free-text query, category, grading service, price/year/grade range, and listing status, in a caller-selected sort order. Only the first 2,400 or so results of a query can be paged through; later pages come back empty and are not charged, so narrow the query with filters. Costs 1 credit per successful call. See GetCategories for the accepted category, grading-service, status, and sort values.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search across title, brand, subject, and set
pageNo1-based page number, default 1
sortNoResult order. Default best_value.
brandNoExact brand/subject facet value (case-insensitive), e.g. a player, character, or set name. Not a fixed enum; match a prior Search result's brand field.
statusNoListing status. Default LIVE.
max_yearNoMaximum card/item year, inclusive
min_yearNoMinimum card/item year, inclusive
per_pageNoResults per page, default 24, max 100
max_gradeNoMaximum numeric grade, inclusive
max_priceNoMaximum current price/bid, inclusive
min_gradeNoMinimum numeric grade, inclusive
min_priceNoMinimum current price/bid, inclusive
seller_idNoExact seller id (UUID) -- browse everything one seller has listed. Not a fixed enum; match a prior Search result's seller_id field.
has_offersNoFilter for listings with at least one active offer pending
auction_urnNoBrowse every lot in one specific weekly or premier auction event. Not a fixed enum; copy the exact value from a prior Search result's auction_urn field. Only WEEKLY/PREMIER listings carry one.
great_priceNoFilter for listings Fanatics Collect itself flags as a great price vs. guide value
marketplaceNoListing type. Omit to search all three.
allow_offersNoFilter for listings the seller accepts offers on
sub_categoryNoA parent > child category path (or just the child name), e.g. \
category_parentNoTop-level category
grading_serviceNoGrading/authentication service
certified_sellerNoExact seller/shop name (case-insensitive). Not a fixed enum -- match a name from a prior Search result's certified_seller field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it discloses the ~2,400-result pagination ceiling, that later pages return empty and are not charged, and that each successful call costs 1 credit. These are the operational facts an agent needs before looping pages and spending credits.

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 tight sentences with the search scope front-loaded, followed by the paging constraint and cost. Dense but every clause carries information; the long middle sentence listing filter axes is the only mild redundancy against 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 22-parameter, no-annotation, no-output-schema tool, the description covers scope, paging limits, credit cost, and where to get valid enum values. Return shape is undocumented, but with 100% schema coverage the remaining gap is minor.

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%, so the schema already documents all 22 parameters, making 3 the baseline. The description adds the useful pointer to GetCategories for enum values and summarizes the filter families, but adds no syntax or format detail beyond the schema.

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?

Specific verb+resource (search Fanatics Collect listings) with explicit scope: weekly auctions, premier auctions, and fixed-price Buy Now. It also enumerates the filter axes (query, category, grading service, ranges, status, sort), which makes it clearly distinguishable from sibling catalog tools like fanaticscollect_listing and fanaticscollect_sold_items.

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?

Gives clear operating context — full-marketplace search, narrow with filters because only ~2,400 results are pageable, and points to GetCategories for accepted enum values. It stops short of naming when to prefer fanaticscollect_sold_items or fanaticscollect_listing instead, so no explicit alternative routing.

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