Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

opensea_collection_holders

Fetches a paginated leaderboard of wallets holding items in an OpenSea collection, ranked by quantity, with each holder's address and display name when available.

Instructions

List an OpenSea collection's holders. Returns a cursor-paginated leaderboard of wallets holding items in the collection, ranked by quantity held, with each holder's address and display name where OpenSea publishes one.

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

Input Schema

Name	Required	Description
`slug`	Yes	OpenSea collection slug
`limit`	No	Holders per page, 1-100
`cursor`	No	Opaque pagination cursor from a previous next_page_cursor
`sort_direction`	No	Sort direction by quantity held

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.17.5Sep 26, 2026
- addedInput schema / properties / sort_direction / enum
```
Added value: +[
+  "ASC",
+  "DESC"
+]
```
Addedv1.16.2Sep 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It transparently mentions cursor-based pagination, ranking by quantity held, and the conditional inclusion of display names. However, it does not cover potential rate limits, authentication requirements, or error behavior, which could matter in practice.

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 compact and efficient: the first sentence states the core purpose, and the second explains the return structure and pagination. Every sentence adds value with no redundant wording.

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 read-only listing tool without an output schema, the description provides sufficient context about the response (leaderboard of wallets, address, display name, ranking, pagination). It does not explicitly define 'holders' (e.g., whether zero-balance wallets are included) or specify defaults for limit/sort_direction, but these are minor gaps given the schema coverage.

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 description coverage is 100%, so the schema already documents all parameters (slug, limit, cursor, sort_direction). The description adds little beyond noting cursor pagination, which is already implied by the cursor parameter's schema description. It meets the baseline but does not exceed it.

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 action ('List an OpenSea collection's holders') with a specific verb and resource. It distinguishes itself from sibling OpenSea tools by focusing on holders rather than traits, depth, or best deals, making its purpose unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives, nor are there any exclusions or conditions mentioned. The description only states what the tool does, leaving the agent to infer usage from the name and description without explicit routing.

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

Deploy Server