Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticscollect_instant_pack_releases

List Fanatics Collect Instant Packs releases with release and checklist IDs, launch times, and listing IDs; use a checklist ID to retrieve product details, checklists, and pull odds.

Instructions

Fanatics Collect Topps Instant Packs releases. Lists the Instant Packs releases currently published by Fanatics Collect with the release ID, checklist ID, launch time and listing ID when available. Pass a checklist ID to fanaticscollect-instant-pack-release for the product details, published checklist and pull odds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fanaticscollect_instant_pack_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It does add real context: only 'currently published' releases are returned (not historical), and fields like listing ID are present only 'when available'. It says nothing about ordering, pagination or result limits, which matters for an unbounded list tool.

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 tight sentences with the listing scope front-loaded and the hand-off to the sibling second. The opening noun fragment largely restates the tool name, though it does add the 'Topps' brand qualifier not present in the name.

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 parameters, no annotations and no output schema, the description usefully enumerates the returned fields and flags conditional availability, which is exactly the gap an absent output schema leaves. Only list size/ordering behavior is unaddressed, a minor omission for a simple read tool.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The only ID mentioned (checklist ID) is an input to the sibling tool, not this one, and the description correctly frames it that way.

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 ('Lists') and resource ('Instant Packs releases currently published by Fanatics Collect'), plus the exact fields returned. It also explicitly separates itself from the sibling fanaticscollect-instant-pack-release, which returns product details, checklist and pull odds.

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?

Gives clear routing guidance: this tool is for the release listing, and a checklist ID should be passed to fanaticscollect-instant-pack-release for deeper product detail. It lacks an explicit 'when not to use' or a statement of what a caller with no checklist ID gets back, but the alternative is named with its condition.

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