Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

comc_listing

Get full COMC card listing details for a card+grade combination, including card identity and all sellers' for-sale copies with owner, item ID, and price. Requires a handle from comc_search.

Instructions

Get COMC card listing detail. Returns one card+grade combination's full detail from COMC (comc.com): card identity and every seller's individual for-sale copy (owner, item id, price). handle is the value returned by comc_search's CardSummary.handle field (or the equivalent comc.com card URL path).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYesRequired. The handle from a comc_search result (or the equivalent comc.com card URL path).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return scope (card identity and seller copies) and the source (comc.com), but does not mention any potential limitations like pagination, rate limits, or data freshness. The description is honest but not deeply transparent.

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 concise and front-loaded with the core purpose. Each sentence adds value, and the parameter explanation is clear without verbosity. No wasted words.

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?

Given the tool has only one parameter and no output schema, the description provides sufficient information for an agent to call it correctly. It explains how to get the handle and what to expect. Minor gaps like output format details are acceptable given the simplicity.

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?

The schema already describes the handle parameter with 100% coverage. The description adds the origin of the handle (from comc_search's CardSummary.handle or URL path), which is helpful but not transformative. Baseline 3 is appropriate since schema already does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves detailed listing information for a COMC card, specifying it returns card identity and seller copies. It distinguishes from the sibling comc_search by referencing the handle from search results, but does not deeply contrast with other siblings.

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 explains when to use this tool (after comc_search) and how to obtain the required handle, providing clear context. It doesn't explicitly mention when not to use it, but the dependency on search results is implicit guidance.

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