Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

tcgplayer_price_history

Retrieve a TCGplayer product's price history by condition, printing and language over month, quarter, half-year or year, including market price, sales volume, transactions and low/high sale prices.

Instructions

Get a TCGplayer product's price history. Returns a TCGplayer product's price history over a month, quarter, half year or year, per condition, printing and language: market price, quantity sold, transaction count and low/high sale price for each period, plus the average daily sales volume.

Input Schema

NameRequiredDescriptionDefault
idYesTCGplayer product id from tcgplayer-search
rangeNoHistory window; defaults to quarter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral load, and it does disclose the aggregation granularity (per condition, printing, language) and the exact metrics returned (market price, quantity sold, transaction count, low/high sale price, average daily sales volume). It stops short of stating the call is read-only or how the data is paginated/limited.

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-loads the purpose in the first sentence and puts return contents in the second; no filler. The second sentence is dense and long but every clause conveys distinct information.

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?

No output schema exists, and the description compensates by enumerating the returned fields and their per-condition/printing/language breakdown. For a 2-parameter read tool, the main remaining gap is that the id's provenance (from tcgplayer-search) lives only in the schema, and no read-only guarantee is stated.

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%, so both parameters are already documented; the description only restates the range values and adds nothing about the 'id' parameter or enum behavior beyond what the schema enum provides. 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?

Names a specific verb+resource (get a TCGplayer product's price history) and enumerates what the history contains, so the agent knows it differs from tcgplayer_product or tcgplayer_sales. It does not explicitly name any sibling, so differentiation is inferred from the content description 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 Guidelines3/5

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

Usage is implied by the content ('price history over a month, quarter, half year or year') but there is no statement of when to prefer this over tcgplayer_sales, tcgplayer_price_guide, or pricecharting_price_history. No prerequisites or exclusions are given.

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