Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

opensea_collection_items

List NFTs in an OpenSea collection with cursor pagination and filters for traits, price, rarity, and listings. Returns owner, listing, and last sale data.

Instructions

List items in an OpenSea collection. Returns a cursor-paginated page of NFTs in a collection with their traits, rarity rank, current owner, best standing listing, and last sale price. Pass cursor from next_page_cursor to page forward. Narrow the result set with listed_only, traits, a min_price/max_price band, or a min_rarity/max_rarity rank band — the filters combine, so traits=Fur:Solid Gold&listed_only=true returns only buyable Solid Gold apes.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	OpenSea collection slug
`limit`	No	Items per page, 1-100
`cursor`	No	Opaque pagination cursor from a previous next_page_cursor
`traits`	No	Comma-separated trait_type:value pairs
`sort_by`	No	Sort field
`max_price`	No	Maximum listing price in the collection's native token
`min_price`	No	Minimum listing price in the collection's native token
`max_rarity`	No	Maximum rarity rank
`min_rarity`	No	Minimum rarity rank (1 is rarest)
`listed_only`	No	Only return items with a standing listing
`sort_direction`	No	Sort direction

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.17.5Sep 26, 2026
- addedInput schema / properties / sort_by / enum
```
Added value: +[
+  "PRICE",
+  "LAST_SALE_DATE",
+  "RARITY",
+  "CREATED_DATE"
+]
```
- addedInput schema / properties / sort_direction / enum
```
Added value: +[
+  "ASC",
+  "DESC"
+]
```
Addedv1.16.2Sep 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It discloses cursor-paginated behavior, returned fields, and filter combination semantics. It omits rate limits, error conditions, and authentication needs, but those are less critical for a read-style list operation.

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?

Three dense sentences, each earning its place: purpose and return shape, pagination instruction, then filter behavior with an example. The description is front-loaded and contains no filler.

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?

The description plus fully-documented schema covers required input, return contents, pagination, and filtering. No output schema exists, but the field list gives a solid picture of the response. It doesn't address sort_by semantics or failure cases, which are either in the schema or non-essential.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema by explaining cursor usage and demonstrating combined filtering with a concrete example ('traits=Fur:Solid Gold&listed_only=true'). This materially helps an agent construct correct queries.

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 ('List') and resource ('items in an OpenSea collection'), then enumerates the page contents: traits, rarity rank, current owner, best listing, and last sale price. This clearly differentiates the general collection-listing tool from more specialized 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?

Provides explicit pagination guidance ('Pass cursor from next_page_cursor to page forward') and explains how filters combine with a concrete example. It does not name alternative sibling tools such as opensea_collection_rarest_items or opensea_collection_best_deals, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

opensea_collection_items

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools