Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticscollect_recently_ripped

Fetch up to 15 recent public Instant Rips card reveals with card and pack titles, item type, time, and images; omit checklist_id for the general feed or pass a pack checklist UUID to narrow results.

Instructions

Fanatics Collect Recently Ripped cards. Fetch up to 15 recent public Instant Rips card reveals with card and pack titles, item type, time and images. Omit checklist_id for the general feed or pass a pack checklist UUID from fanaticscollect_instant_rips_packs to narrow the feed. An uncovered pack can return an empty list.

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_recently_ripped"
  }
}

Input Schema

NameRequiredDescriptionDefault
checklist_idNoPack checklist UUID from the pack catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the burden. It does disclose useful traits: the 15-result cap, public-only scope, and empty-list behavior for uncovered packs. It omits ordering of results, pagination behavior, and any auth or rate-limit notes.

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?

Three short sentences, front-loaded with what is returned and its size cap, followed by the filtering rule. Efficient overall; the opening sentence mostly repeats the tool title instead of leading with the verb.

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?

For a one-optional-parameter list tool with no output schema, the description covers scope, result cap, filter semantics, and the empty-result case. Result ordering and pagination remain unspecified, but nothing critical to a correct call is missing.

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 single parameter already describes itself as a pack checklist UUID from the pack catalog. The description restates that and adds the omit-versus-pass semantics and the empty-result consequence, adding modest value beyond the schema.

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: 'Fetch up to 15 recent public Instant Rips card reveals' and enumerates the returned fields (card and pack titles, item type, time, images). It also distinguishes itself from the sibling fanaticscollect_instant_rips_packs, which supplies the checklist UUID.

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?

Explicitly gives the two usage modes: omit checklist_id for the general feed, or pass a UUID from fanaticscollect_instant_rips_packs to narrow it, plus the edge case that an uncovered pack may return an empty list. It does not compare against other recent-item siblings such as sold_items or search, but the in-scope choice is unambiguous.

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