Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opensea_profile_created

Retrieve all NFT collections a wallet created, including floor price and trading stats, to map a creator's full body of work from any contract deployer address.

Instructions

List the collections a wallet created. Returns the collections a wallet created, as opposed to the ones it holds, each with its floor price and trading statistics. Use this to find a creator's full body of work from any one of their collections' contract deployer address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoCollections per page, 1-100
cursorNoOpaque pagination cursor from a previous next_page_cursor
sort_byNoSort field
identifierYesWallet address, ENS name, or OpenSea username
sort_directionNoSort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort_by / enum
      Added value: +[
+  "VOLUME",
+  "ONE_DAY_VOLUME",
+  "FLOOR_PRICE",
+  "SALES"
+]
    • addedInput schema / properties / sort_direction / enum
      Added value: +[
+  "ASC",
+  "DESC"
+]
  2. Addedv1.16.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It does disclose that the tool returns collections with floor price and trading statistics, and that it focuses on created rather than held collections. However, it does not mention pagination, rate limits, authentication needs, or explicitly confirm read-only behavior, leaving some behavioral details implicit.

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 in the first sentence. The second sentence adds useful distinguishing and output details, and the third gives a concrete use case. There is minor redundancy between the first and second sentences, but overall it is efficient.

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 list tool with fully documented parameters, the description adequately explains what is returned, how it differs from holdings, and when to use it. It does not discuss pagination or sort behavior, but those are covered by the input schema, and the lack of an output schema is partially compensated by mentioning floor price and trading statistics.

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 parameters are already well documented. The description adds minimal parameter-level value beyond mentioning that the identifier can be a contract deployer address; it mostly reinforces usage rather than clarifying parameter meanings.

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 and resource: 'List the collections a wallet created.' It also distinguishes itself from the alternative of listing collections a wallet merely holds, which separates it from sibling profile/collection tools. The mention of floor price and trading statistics further clarifies the returned content.

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 a clear use case: 'Use this to find a creator's full body of work from any one of their collections' contract deployer address.' It contrasts created collections vs. held ones, giving context for when this tool is appropriate, though it does not explicitly name alternative sibling tools or state when not to use it.

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