Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

tcgplayer_search

Search TCGplayer’s trading-card catalog by product line, set, rarity, type, or price range to retrieve product IDs, market and listing prices, links, and filter facets.

Instructions

Search TCGplayer trading-card products. Searches TCGplayer's catalog of trading-card and collectible products (Pokemon, Magic, Yu-Gi-Oh!, One Piece, Lorcana and about 70 other product lines) and returns one page of matches: product id, name, set, rarity, card number, market, lowest and median prices, listing count, links and filter facets. Filter by product line, set, product type, rarity, card type and price range, and sort by price, listings, sales or name.

Input Schema

NameRequiredDescriptionDefault
qNoSearch text, up to 100 characters; optional when product_line is set
setNoSet url_name from tcgplayer-sets; needs product_line
sortNoSort field; omit for relevance
limitNoPage size, 1 to 50; defaults to 24
orderNoSort direction, needs sort; default desc (asc for product-name)
offsetNoResults to skip; offset plus limit must be 9999 or less
rarityNoExact rarity label such as Holo Rare; see facets.rarities
card_typeNoExact card type label such as Pokemon; see facets.card_types
max_priceNoMaximum market price in US dollars
min_priceNoMinimum market price in US dollars
product_lineNoProduct line url_name from tcgplayer-product-lines, for example pokemon, magic, yugioh
product_typeNoExact product type label such as Cards or Booster Box; see facets.product_types

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full disclosure burden, and it does meaningful work: it declares the result is a single page (not an exhaustive dump), enumerates the returned fields including pricing, listing counts and facets, and warns indirectly that filter labels must match exact facet values. It omits freshness of price data and any rate-limit or auth expectations.

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?

Two sentences, front-loaded with the core action and its scope, then the return payload and filter/sort axes. The parenthetical product-line roster ('Pokemon, Magic, Yu-Gi-Oh!, One Piece, Lorcana and about 70 other product lines') is the only mildly expendable clause, though it does convey catalog breadth.

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 12 optional parameters and no output schema, the description does the necessary compensating work by listing the shape of a result row and confirming facets are returned for follow-up filtering. Missing only price-data freshness/currency context and any failure or empty-result behavior.

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 every parameter already carries a precise description, including the enum values for sort and the offset/limit ceiling. The description restates the filter axes (product line, set, product type, rarity, card type, price range) and sort options but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 TCGplayer trading-card products') and pins the scope to a catalog-wide paged search, which implicitly separates it from detail-oriented siblings such as tcgplayer_product, tcgplayer_listings and tcgplayer_price_guide. It never names an alternative tool, so the differentiation is inferred rather than stated.

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 useful invocation context — 'q' is optional when product_line is set, set values come from tcgplayer-sets, product_line from tcgplayer-product-lines, and rarity/card_type/product_type come from returned facets — which effectively routes the agent to the right sibling tools for resolving filter values. It stops short of explicit when-not-to-use guidance or naming which sibling replaces this search.

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