Crawlora MCP

tcgplayer_sets

Read-only

List the active sets (expansions) of one TCGplayer product line, newest first, and return each set's name, the url_name that tcgplayer_search takes as set, the abbreviation and the release date. Use this to discover valid set values for a product line.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_line": "<product_line>"
    },
    "name": "tcgplayer_sets"
  }
}

Input Schema

Name	Required	Description	Default
`product_line`	Yes	Product line url_name from tcgplayer-product-lines

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavior: only *active* sets are returned and they are ordered newest-first, which affects result expectations. It stops short of describing pagination or how 'active' is determined, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the operation and ordering front-loaded before the usage note. Every clause (active, newest first, four returned fields, search linkage) carries information.

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?

An output schema exists, so explaining return values was optional and the description does it anyway; safety is covered by annotations and the single param by schema. The only gap is what 'active' excludes (retired/upcoming sets), which an agent might want before deciding the result is exhaustive.

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 product_line parameter already documents 'Product line url_name from tcgplayer-product-lines', so the schema carries the semantic load. The description only restates 'one TCGplayer product line' without adding format or example values, which is the expected baseline 3.

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 ('List the active sets (expansions) of one TCGplayer product line'), plus scope (one product line), ordering (newest first), and the returned fields. That is enough for an agent to distinguish it from tcgplayer_product_lines (which supplies the input) and tcgplayer_search (which consumes the output).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

'Use this to discover valid set values for a product line' names the exact situation for calling it, and the description closes the loop by saying the returned url_name is what tcgplayer_search takes as set. The workflow position between product_lines and search is explicit rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?