Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tcgplayer_product_lines

List TCGplayer product lines, including game and product-family IDs, names, and url_names, to retrieve the product_line values required by search and set tools.

Instructions

List TCGplayer product lines. Lists TCGplayer's product lines (games and product families such as Pokemon, Magic: The Gathering, Yu-Gi-Oh!, One Piece and Lorcana): id, name and the url_name that tcgplayer-search and tcgplayer-sets take as product_line.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/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 burden: it discloses that this is a pure enumeration with no inputs and specifies exactly which fields come back (id, name, url_name). It does not mention ordering, pagination, or rate limits, which are minor for a small zero-argument catalog listing.

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?

Two sentences, front-loaded with the verb and resource, then dense with examples and field names. The opening 'List TCGplayer product lines.' partially restates the second sentence, a small redundancy, but no other waste.

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 no output schema, the description compensates by naming the returned fields and their downstream use, which is what an agent needs to chain calls. Only ordering or completeness guarantees (e.g., whether the list is exhaustive) are missing.

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?

The tool takes zero parameters, which is the baseline-4 case. Rather than describing inputs, the description usefully documents the output identifier semantics (url_name feeds other tools), adding value where the schema is empty.

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 ('List TCGplayer product lines') with concrete examples of what a product line is (Pokemon, Magic, Yu-Gi-Oh!, One Piece, Lorcana). It also names the return fields and the sibling tools that consume the identifier, so an agent can distinguish it from tcgplayer-search and tcgplayer-sets without reading schemas.

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?

The description makes the usage path clear by stating that the returned url_name is what tcgplayer-search and tcgplayer-sets take as product_line, implying this is the lookup/enumeration step before those calls. It stops short of an explicit 'call this first' or a statement of when not to use it.

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