Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

tcgplayer_sales

Get a TCGplayer product's five most recent completed sales with condition, printing, language, quantity, price, shipping, and order time; optionally filter by condition, variant, language, or photos

Instructions

Get a TCGplayer product's most recent sales. Returns the five most recent completed sales of a TCGplayer product: condition, printing, language, quantity, sale price, shipping price and order time. Optionally restrict to one condition (near-mint, lightly-played, moderately-played, heavily-played, damaged or unopened), one printing (variant such as Normal, Foil or Reverse Holofoil), one language (such as English or Japanese) and whether the listing had photos. The printing and language values a product accepts come from tcgplayer-filters; an unlisted value returns invalid parameters. A variant or language filter makes one extra call to read the product line's filter values.

Input Schema

NameRequiredDescriptionDefault
idYesTCGplayer product id from tcgplayer-search
variantNoPrinting label of the product's product line, such as Normal, Foil, Holofoil or Reverse Holofoil; see tcgplayer-filters
languageNoLanguage label: English, Chinese (S), Chinese (T), French, German, Italian, Japanese, Korean, Portuguese, Russian or Spanish, limited to the languages of the product's line; see tcgplayer-filters
conditionNoCondition filter
listing_typeNoListing type filter; default all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden: it discloses the exact result size (five most recent completed sales), the returned fields, the filter behavior, that unlisted values return invalid parameters, and that variant or language filters trigger one extra call. It does not mention authentication or rate limits, but for a public read-only sales lookup these omissions are minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loads the core purpose, then details return values, optional filters, and filter constraints. Every sentence adds useful information with no filler.

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?

No output schema exists, so the description must explain return values, and it does so completely by listing condition, printing, language, quantity, sale price, shipping price, and order time, plus the fixed count of five. Combined with the parameter behavior and fallback source for filter values, an agent has enough information to call it correctly.

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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by stating that valid printing and language values come from tcgplayer-filters, that unlisted values return invalid parameters, and that variant or language filters cause an extra call. It also restates the condition options, but the extra behavioral constraints justify a 4.

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?

The description states a specific verb and resource: 'Get a TCGplayer product's most recent sales.' It further scopes the result to 'the five most recent completed sales' and lists the returned fields. This distinguishes it from sibling tools like tcgplayer_listings (current listings) and tcgplayer_price_history (historical prices), even without naming them.

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?

The description makes clear this is for recent completed sales and that variant/language filters require values from tcgplayer-filters. However, it does not explicitly say when to use this tool instead of siblings such as tcgplayer_price_history or tcgplayer_listings, nor does it state exclusions.

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