Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tcgplayer_sets

List active sets for a TCGplayer product line, ordered by release date, with set names, URL names, abbreviations, and release dates. Use it to find the set value needed for TCGplayer searches.

Instructions

List the sets of a TCGplayer product line. Lists the active sets (expansions) of one TCGplayer product line, newest first: name, the url_name that tcgplayer-search takes as set, abbreviation and release date.

Input Schema

NameRequiredDescriptionDefault
product_lineYesProduct line url_name from tcgplayer-product-lines

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/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 and does reasonably: it discloses that only active sets are returned, that ordering is newest first, and enumerates the returned fields (name, url_name, abbreviation, release date). It stops short of stating whether inactive/sold-out sets are omitted entirely or paginated.

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 and front-loaded with the scope, but the first sentence is largely repeated by the second ('List the sets of a TCGplayer product line' vs 'Lists the active sets ... of one TCGplayer product line'), a small redundancy.

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?

Single required parameter, no output schema, and the description already names the returned fields plus ordering and the active-only filter, so an agent can call it correctly. Only pagination/response-shape details are left implicit.

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% and the schema already explains product_line as a url_name from tcgplayer-product-lines. The description restates the same provenance and adds only the downstream use of url_name as a set filter, so the 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?

States a specific verb (List) and resource (sets of a TCGplayer product line) and scopes it to 'active sets (expansions)'. Names the returned fields and ties the tool to sibling tcgplayer-search via url_name, so it is distinguishable from tcgplayer_product_lines and tcgplayer_search.

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?

Implies usage by noting that url_name is what tcgplayer-search takes as set, which hints at the workflow, but it never explicitly says when to call this instead of tcgplayer-product-lines or price-guide tools, and gives no exclusions.

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