Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

opensea_collection_top_sales

Retrieve an OpenSea collection's sales ranked by sale price, including buyer, seller, price, and transaction hash for each transaction.

Instructions

List an OpenSea collection's highest-value sales. Returns the highest-value sales ever recorded for a collection, with the buyer, seller, price, and transaction hash for each. Unlike /opensea/collection/{slug}/activity?event_types=SALE, which is a reverse-chronological feed, this is ranked by sale price.

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": {
      "slug": "<slug>"
    },
    "name": "opensea_collection_top_sales"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	OpenSea collection slug

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full load. It discloses the return fields (buyer, seller, price, transaction hash) and the ordering behavior. It doesn't mention pagination or limits, but the core behavior is made transparent and there are no misleading side effects.

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?

Two sentences, with the action and resource front-loaded, followed by output details and a clear comparison. Every clause serves a purpose; no fluff.

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 tool with no output schema, the description covers purpose, output contents, and the key behavioral distinction from the sibling feed. The only minor gap is result limits/pagination, which is not critical for a first invocation.

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% for the single `slug` parameter, so the baseline is 3. The description reinforces that slug identifies a collection but adds no format details or examples 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?

The description uses a specific verb ('List') and resource ('an OpenSea collection's highest-value sales'). It explicitly distinguishes itself from the activity feed by noting the ranking basis, so an agent can tell it apart from opensea_collection_activity without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative endpoint (`/opensea/collection/{slug}/activity?event_types=SALE`) and states the differentiator: reverse-chronological feed vs. ranked by sale price. This gives a clear when-to-use vs. when-not-to-use rule.

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

Deploy Server