Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opensea_collection_activity

Fetch a cursor-paginated feed of an OpenSea collection's marketplace activity—sales, listings, offers, transfers, and mints—and filter by event type for targeted history.

Instructions

List an OpenSea collection's marketplace activity. Returns a cursor-paginated feed of marketplace events for a collection — sales, listings, offers, transfers, mints, and collection/trait offers — with the counterparties, price, marketplace, and transaction hash. Filter with event_types to narrow the feed, for example event_types=SALE for a sales-only history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesOpenSea collection slug
limitNoEvents per page, 1-100
cursorNoOpaque pagination cursor from a previous next_page_cursor
event_typesNoComma-separated event types

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / event_types / enum
      Added value: +[
+  "SALE",
+  "LISTING",
+  "OFFER",
+  "TRANSFER",
+  "MINT",
+  "COLLECTION_OFFER",
+  "TRAIT_OFFER"
+]
  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 full burden. It discloses that the response is a cursor-paginated feed and lists included fields, but it does not explicitly state the operation is read-only or mention any rate limits or authentication requirements. 'List' and 'Returns' strongly imply read-only, so there is no contradiction.

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 two sentences, with the core purpose in the first sentence and filtering guidance in the second. Every sentence contributes meaningful information with no redundancy or 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?

Given the absence of an output schema, the description compensates by listing return fields (counterparties, price, marketplace, transaction hash) and mentioning pagination. It could add more detail on cursor usage or default limits, but these are partly covered by the input schema, making the overall description adequate.

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

Parameters4/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. The description adds value by enumerating the event types in prose and providing a concrete filtering example, which clarifies the enum and helps an agent understand how to narrow results.

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 states 'List an OpenSea collection's marketplace activity' with a specific verb and resource, and enumerates the event types (sales, listings, offers, transfers, mints). It is clear but does not explicitly name or differentiate from sibling tools like opensea_activity or opensea_profile_activity, though the collection scope is implied.

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 clear context for filtering with event_types and gives an example (event_types=SALE). However, it does not specify when to choose this tool over alternatives or mention any exclusions, so it stops short of full guidance.

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