Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opensea_collection_best_deals

Find OpenSea collection listings that OpenSea marks as good value based on rarity, not just price. Provide a collection slug to see curated deals.

Instructions

List an OpenSea collection's best-value listings. Returns the listed items OpenSea surfaces as the best value in a collection, judged against each item's rarity and the collection floor. This is the curated "best deals" shelf from the collection page, not a generic price sort.

Input Schema

NameRequiredDescriptionDefault
slugYesOpenSea collection slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations available, the description carries the full burden and it does well by disclosing the selection criteria and the curated nature of the output. It explains that results come from a defined shelf, not an arbitrary sort, which is meaningful behavioral context.

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?

The description is compact and front-loaded, with each of the three sentences adding relevant information. There is a minor overlap between 'best-value listings' and 'curated best deals', but it is lean overall and will help an agent quickly grasp the tool.

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 single-parameter list tool with no output schema, the description sufficiently conveys what the tool returns and the mental model of how results are chosen. It could mention pagination or count, but that is not essential given the simple interface and clear semantics.

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 only parameter, slug, is fully described in the input schema itself (100% schema coverage). The tool description adds no extra detail about the parameter beyond 'OpenSea collection slug', so it meets the baseline without adding value.

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 clearly states the tool lists an OpenSea collection's best-value listings and explicitly labels it as the curated 'best deals' shelf from the collection page. It also distinguishes itself from a generic price sort, which is enough to separate it from sibling tools like opensea_collection_rarest_items or opensea_collection_top_sales.

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?

The description provides clear context: this is the curated 'best deals' shelf, tailored by rarity and collection floor, and explicitly excludes 'a generic price sort'. While it doesn't name alternative OpenSea tools, the exclusion and definition give an agent a strong signal about when this tool is relevant.

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