Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pricecharting_product

Retrieve a PriceCharting product's current prices by condition or grade, full price guide, attributes, and recent eBay and TCGplayer sales by ID, URL, or console and slug.

Instructions

Get a PriceCharting product's prices and recent sales. Returns one PriceCharting product page: current prices by condition or grade with their latest change, the full price guide, attributes (publisher, release date, card number and similar) and the most recent completed eBay and TCGplayer sales per grade. 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 search or console results; costs one extra request to resolve
urlNoA pricecharting.com product page address, instead of id or console and slug
slugNoProduct slug from pricecharting.com/game/<console>/<slug>; use with console
consoleNoConsole or set slug (for example pokemon-base-set); use 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 burden and does reasonably well: it discloses the return payload shape and adds a non-obvious behavioral requirement — attribute PriceCharting as the data source with a link when displaying. It omits auth/rate-limit or partial-result behavior, but for a read-only lookup that is a modest gap.

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?

Lead sentence states the result up front, and each following sentence covers a distinct concern (payload contents, lookup modes, attribution). Slightly dense in the middle inventory sentence, but nothing is redundant.

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 characterize returns — and it does so thoroughly by enumerating price, guide, attributes, and recent sales. It leaves open whether the full price guide is paginated or truncated, which is the only substantive omission for a complex page fetch.

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 description coverage is 100%, so all four parameters are already documented with formats and the cost note on id. The description only restates the three lookup modes, adding no syntax or constraint beyond the schema. Baseline 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?

Specific verb plus resource: 'Get a PriceCharting product's prices and recent sales', followed by an explicit inventory of what the page returns (current prices by condition/grade, price guide, attributes, recent eBay and TCGplayer sales). It is clearly distinguishable from pricecharting_search (lookup) and pricecharting_price_history (time series).

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?

It gives three concrete lookup routes (id, pricecharting.com URL, or console + slug), which is real usage guidance. It stops short of stating when to prefer this tool over pricecharting_search or pricecharting_console first, or what to do when a lookup fails, so it is clear context without explicit alternatives.

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