Crawlora MCP

tcgplayer_product

Read-only

Get one TCGplayer product's full detail by product id: name, product line, set, rarity, card number, plain-text card description, attributes, market, lowest and median prices, listing and seller counts, every condition/variant/language SKU, and market and buylist price per printing. Use after tcgplayer_search to read a card's details and price.

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_product"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	TCGplayer product id (the number in tcgplayer.com/product/<id>), from tcgplayer-search

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.

AddedOct 26, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and world-access profile are covered. The description adds that the response spans every condition/variant/language SKU and per-printing buylist pricing, which usefully signals a large, exhaustive payload, but says nothing about auth, rate limits, or failure modes for an unknown id.

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 operation and ending with the routing cue. The long mid-sentence field enumeration is dense and partially duplicates the output schema, but it is not padded prose.

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 a single required, fully documented parameter, an output schema, and safety annotations, the description supplies everything needed to invoke the tool correctly plus a workflow pointer. The only redundancy is that listing return fields is already handled by the output schema.

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 schema already explains the id is the number in tcgplayer.com/product/<id> sourced from search. The description only restates "by product id," adding no format, validation, or lookup-failure semantics beyond the schema — baseline 3.

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 one TCGplayer product's full detail by product id") and enumerates the returned content — identity fields, pricing, listing/seller counts, and per-printing SKU pricing. An agent can distinguish this lookup from search/listing/price-guide siblings without opening any 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?

Explicitly positions the tool in a workflow: "Use after tcgplayer_search to read a card's details and price," which names both the prerequisite and the alternative. It does not address when to prefer siblings like tcgplayer_listings or tcgplayer_price_guide, so it falls short of full when/when-not coverage.

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?