Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

opensea_profile_collections

List the NFT collections a wallet holds, with item counts and current floor prices, to value holdings collection by collection.

Instructions

List the collections a wallet holds. Returns the collections a wallet holds items in, with how many items it holds in each and that collection's current floor price. Useful for valuing a wallet's holdings collection by collection.

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": {
      "identifier": "<identifier>"
    },
    "name": "opensea_profile_collections"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Collections per page, 1-100
`cursor`	No	Opaque pagination cursor from a previous next_page_cursor
`identifier`	Yes	Wallet address, ENS name, or OpenSea username

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

B3.4/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 burden. It discloses that results include item counts and floor prices, and that pagination is supported via cursor. However, it doesn't mention whether the wallet must be indexed, rate limits, or what happens for invalid identifiers.

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 the core action. The second sentence adds useful context about valuation use case. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list endpoint with pagination parameters and no output schema, the description covers the basics but lacks details about response shape, sorting, or edge cases. It's adequate but not comprehensive.

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%, so the schema already documents all three parameters. The description adds no extra meaning beyond what the schema provides, which is acceptable but not additive.

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 lists collections a wallet holds, with item counts and floor prices. It distinguishes itself from related OpenSea tools like opensea_collection (single collection details) and opensea_profile_items (individual items), though it doesn't explicitly name a sibling.

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

Usage Guidelines3/5

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

The description implies usage for valuing a wallet's holdings collection by collection, which gives context for when to use it. However, it doesn't explicitly state when not to use it or name alternative tools like opensea_profile_items or opensea_collection_holders.

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

Deploy Server