Crawlora MCP

fanaticscollect_instant_pack_release

Read-only

Fetch a Fanatics Collect Topps Instant Pack release by checklist_id from fanaticscollect_instant_pack_releases. Returns its title, launch time, status, checklist link, published odds and price when supplied. Unknown checklists return not found. Use the list tool to get the checklist ID; listing and release IDs identify different records.

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": {
      "checklist_id": "<checklist_id>"
    },
    "name": "fanaticscollect_instant_pack_release"
  }
}

Input Schema

Name	Required	Description	Default
`checklist_id`	Yes	Required. Checklist UUID returned by fanaticscollect_instant_pack_releases.

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.

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavior by noting the optional return fields and that unknown checklists return not found, though it does not describe auth, rate limits, or upstream failure behavior.

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?

The description is front-loaded and appropriately brief for a single-parameter lookup. Each sentence adds value: what is fetched, what is returned, the not-found behavior, and how to obtain the correct ID.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required parameter, full schema coverage, an output schema, and annotations, the description supplies everything else an agent needs. It covers the ID source, return contents, optional fields, and the not-found case without redundant detail.

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 schema documents the single checklist_id parameter at 100% coverage, so the baseline is satisfied. The description adds meaningful semantics by tying the ID to the list tool and clarifying that release IDs are a different identifier type.

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?

The description states a specific verb and resource: fetch a Fanatics Collect Topps Instant Pack release by checklist_id from the named collection. It also distinguishes this detail lookup from the list operation and warns that listing and release IDs identify different records.

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?

It clearly explains that the checklist ID should come from the list tool and warns against confusing listing IDs with release IDs. The guidance is strong but does not explicitly state when not to use this tool beyond the ID-source warning.

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?