Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tcgplayer_product

Retrieve a TCGplayer product by ID, including name, set, rarity, card text, market/lowest/median prices, SKU conditions, and buylist prices for pricing and catalog checks.

Instructions

Get a TCGplayer product's detail and price points. Returns one TCGplayer product in full: name, product line, set, rarity, card number, card text, attributes, the market, lowest and median prices, listing and seller counts, every purchasable condition/variant/language SKU, and TCGplayer's market and buylist price per printing.

Input Schema

NameRequiredDescriptionDefault
idYesTCGplayer product id (the number in tcgplayer.com/product/<id>), from tcgplayer-search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/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 burden, and it does disclose a detailed inventory of what comes back: pricing fields, listing/seller counts, per-condition SKU enumeration, market and buylist prices per printing. It omits any note on auth, rate limits, or whether the data is a live snapshot versus cached, which keeps it short of a 5.

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?

Front-loaded with the core verb and purpose, then a single dense enumeration sentence. Every clause carries information, though the enumeration runs long and could have been split for readability.

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?

With no output schema and no annotations, the field-level enumeration is exactly what an agent needs to decide whether this tool answers a price/SKU question. For a single-parameter lookup tool, nothing material 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% for the single id parameter, and the schema itself explains the format and provenance (tcgplayer-search). The description adds no additional meaning about the parameter, so the baseline of 3 applies.

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 (get) and resource (a TCGplayer product) and then enumerates the returned fields, which implicitly separates it from sibling price tools like tcgplayer_price_history and tcgplayer_sales by signaling a current snapshot rather than a time series. An agent can tell what this returns without opening the schema.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not language, and no sibling tool is named as an alternative. The usage is only implied — the workflow of finding an id via search and then fetching detail is suggested indirectly by the id parameter's note ('from tcgplayer-search') rather than by the description itself.

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