Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tcgplayer_listings

Lists current sellers for a TCGplayer product, including seller rating, condition, printing, language, quantity, price, and shipping, with filters and price sorting to compare offers.

Instructions

List the sellers offering a TCGplayer product. Returns one page of the current seller listings for a TCGplayer product: seller storefront name, rating and sales volume, condition, printing, language, quantity, price, shipping price and seller location. Filter by condition, printing and language, and sort by price or price with shipping.

Input Schema

NameRequiredDescriptionDefault
idYesTCGplayer product id from tcgplayer-search
sortNoSort field; omit for TCGplayer's own order
limitNoPage size, 1 to 50; defaults to 24
orderNoSort direction, needs sort; default asc
offsetNoListings to skip; offset plus limit must be 9999 or less
languageNoExact language label such as English; see facets.languages
printingNoExact printing label such as Normal or Foil; see facets.printings
conditionNoCondition filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the key behavioral facts: results are 'one page' (pagination), and it enumerates the returned fields including seller rating, sales volume, shipping price and location. It says nothing about auth needs, rate limits, or whether the data is a live snapshot vs cached, and the 9999 offset+limit ceiling lives only in the schema.

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?

Three tight sentences with the core action front-loaded. The second sentence slightly re-states the first ('List the sellers...' / 'Returns one page of the current seller listings'), but the waste is minor.

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 8 params, no output schema and no annotations, the description does useful work by enumerating the return payload, which the missing output schema would otherwise leave opaque. It omits pagination mechanics and result-ordering caveats, keeping it short of fully complete.

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 every parameter is already documented, including enum values and the id's origin. The description restates the filter and sort axes ('condition, printing and language', 'price or price with shipping') without adding format or edge-case guidance, so 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?

States a specific verb and resource: 'List the sellers offering a TCGplayer product', which clearly distinguishes it from price-guide or sales-history siblings. It never names a sibling explicitly, but the resource is unambiguous.

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?

The description explains how to narrow results ('filter by condition, printing and language, and sort by price or price with shipping') but never says when to choose this over tcgplayer_sales, tcgplayer_price_history or tcgplayer_product. Usage is implied rather than stated.

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