Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pricecharting_price_history

Retrieve a PriceCharting product's dated monthly price series by ID, URL, or console and slug to analyze trading card or video game price trends and grade population counts.

Instructions

Get a PriceCharting product's monthly price history. Returns the monthly price history behind a PriceCharting product page's price chart: one series per price column (for a trading card Ungraded, Grade 7, Grade 8, Grade 9, Grade 9.5 and PSA 10; for a video game Loose, Complete, New, Graded, Box and Manual), each a list of dated prices, oldest first, starting wherever PriceCharting's chart starts for that product. Trading cards also carry the PSA and CGC population counts by grade 1 to 10. Look a product up by id, by its pricecharting.com address, or by console and slug. Price data is PriceCharting's; cite it with a link when you display it.

Input Schema

NameRequiredDescriptionDefault
idNoPriceCharting product id from pricecharting-search or pricecharting-console (costs one extra request)
urlNoA pricecharting.com/game/<console>/<slug> product address
slugNoProduct slug, used together with console
consoleNoConsole or set slug, used together with slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/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 load and does well: it discloses that the series start 'wherever PriceCharting's chart starts' (no guaranteed date range), that ordering is oldest-first, that trading cards additionally return PSA/CGC population counts by grade, and that the data must be attributed with a link. It does not cover failure behavior for an unknown product or whether the extra id-lookup request costs quota, but the substantive data-shape contract is present.

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 purpose, then return shape, then lookup modes, then the citation requirement — a sensible order. Five dense sentences with no filler, though the return-shape sentence is long enough that an agent skimming may miss the lookup-mode sentence.

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, so the description must describe the return, which it does in detail (per-column series, ordering, start point, population counts). Combined with 100% schema coverage and zero annotations, the remaining gaps are minor — chiefly no guidance on resolving a product to an id and no statement of what happens when the lookup fails.

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 coverage is 100%, so baseline is 3, but the description adds a framing beyond the schema: the three identification paths (id, pricecharting.com URL, console+slug) are presented as alternatives an agent can pick from. It does not add format examples or warn about combining url with id, but it usefully elevates the lookup modes above field-level text.

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 a PriceCharting product's monthly price history') and then enumerates exactly what the return contains, including the per-column series names for both trading cards and video games. This is distinguishable from siblings like pricecharting_product (current data) or pricecharting_big_movers 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 Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the tool for historical/chart data on a known product. There is no explicit 'use this instead of X' routing and no mention that pricecharting_search or pricecharting_console is needed first to obtain an id — that hint lives only in the schema, not the description. The sibling set (pricecharting_product, pricecharting_search, tcgplayer_price_history) is never referenced.

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