Crawlora MCP

tcgplayer_sales

Read-only

Get the five most recent completed sales of one TCGplayer product by product id: condition, printing, language, quantity, sale price, shipping price and order time. Optionally restrict to one condition (including unopened for sealed product), one printing (variant such as Normal, Foil or Reverse Holofoil), one language, or listings with or without photos; get the variant and language values a product accepts from tcgplayer_filters. Use this to see what a card actually sold for lately; use tcgplayer_price_history for the trend.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "tcgplayer_sales"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	TCGplayer product id from tcgplayer-search
`variant`	No	Printing label of the product's product line, such as Normal, Foil, Holofoil or Reverse Holofoil; see tcgplayer-filters
`language`	No	Language 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
`condition`	No	Condition filter. Documented values: near-mint, lightly-played, moderately-played, heavily-played, damaged, unopened.
`listing_type`	No	Listing type filter; default all. Documented values: all, with-photos, without-photos.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / condition / description

Previous value: -"Condition filter. Documented values: near-mint, lightly-played, moderately-played, heavily-played, damaged."New value: +"Condition filter. Documented values: near-mint, lightly-played, moderately-played, heavily-played, damaged, unopened."

addedInput schema / properties / language

Added value: +{
+  "description": "Language 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",
+  "type": "string"
+}

addedInput schema / properties / listing_type

Added value: +{
+  "description": "Listing type filter; default all. Documented values: all, with-photos, without-photos.",
+  "type": "string"
+}

addedInput schema / properties / variant

Added value: +{
+  "description": "Printing label of the product's product line, such as Normal, Foil, Holofoil or Reverse Holofoil; see tcgplayer-filters",
+  "type": "string"
+}

AddedOct 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description adds real behavioral detail: results are capped at five, ordered by recency, are completed (not active) sales, and each filter is an optional single-value restriction. It does not discuss empty-result behavior for sparse products, which is the only remaining gap.

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?

Three sentences, each earning its place: capability and return shape first, optional filters second, decision guidance last. 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?

A read-only, tool with an output schema, five fully documented params; the description covers scope, return shape, filter behavior, and sibling routing. Nothing an agent needs to invoke it correctly is missing.

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 already documents every filter with examples and the tcgplayer-filters pointer, so the description mostly restates it. It adds only the nuance that 'unopened' applies to sealed product and that variant/language are constrained to the product's line.

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 ('Get the five most recent completed sales of one TCGplayer product by product id') and enumerates the returned fields, which distinguishes it from price-oriented siblings.

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

Usage Guidelines5/5

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

Explicitly names the alternative and the condition that selects it: 'Use this to see what a card actually sold for lately; use tcgplayer_price_history for the trend.' It also routes the agent to tcgplayer_filters for valid variant and language values.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?