Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opensea_drops

Retrieve the OpenSea NFT drop calendar to track upcoming mints or recently minted drops, including contract, chain, and parent collection details.

Instructions

List the OpenSea drop calendar. Returns the NFT drop calendar — either upcoming mints or recently minted drops — with each drop's contract, chain, and parent collection. Use type=UPCOMING to watch for launches and type=RECENTLY_MINTED for ones that just went live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoCalendar window
limitNoDrops per page, 1-100
cursorNoOpaque pagination cursor from a previous next_page_cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "UPCOMING",
+  "RECENTLY_MINTED"
+]
  2. Addedv1.16.2

TDQS

A4.2/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 burden, and it does convey a read-only list operation ('List'/'Returns') and the two calendar windows. However, it does not disclose pagination behavior, defaults, ordering, or how the cursor interacts with the returned calendar, leaving some behavioral ambiguity.

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 focused sentences with no filler. The description front-loads the action and resource, then immediately covers the type choices and return fields, earning every word.

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 simple read-only calendar tool with no required parameters, the description covers the resource, the two modes, and the key returned fields. It could explicitly mention pagination, but the schema already documents `limit` and `cursor`, so the essential context for selecting and invoking the tool is present.

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 valuable semantics to the `type` enum beyond the schema's terse 'Calendar window' by explaining UPCOMING vs RECENTLY_MINTED in practical terms. The `limit` and `cursor` parameters are already well described in 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?

States a specific verb and resource: 'List the OpenSea drop calendar.' It further specifies the two calendar modes (UPCOMING and RECENTLY_MINTED) and the returned fields (contract, chain, parent collection), making it clearly distinct from the other OpenSea sibling tools.

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?

Gives explicit guidance for when to use each type value: `type=UPCOMING` for watching launches and `type=RECENTLY_MINTED` for recently live drops. It does not discuss exclusions or alternatives, but no sibling tool covers the drop calendar, so this is sufficient context.

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