Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opensea_item_listings

Fetch active sell orders for any OpenSea NFT, returning price, quantity, validity, marketplace, and maker wallet. Empty list when no listings exist.

Instructions

List standing listings for an OpenSea NFT. Returns every standing sell order for one NFT, with price, quantity, validity window, marketplace, and the maker's wallet. An item with no active listings returns an empty list rather than a 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesChain identifier from /opensea/chains
limitNoListings per page, 1-100
cursorNoOpaque pagination cursor from a previous next_page_cursor
token_idYesToken id within the contract
sort_directionNoSort direction by price
contract_addressYesNFT contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort_direction / enum
      Added value: +[
+  "ASC",
+  "DESC"
+]
  2. Addedv1.16.2

TDQS

A4.2/5.0
Behavior4/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 the returned fields (price, quantity, validity window, marketplace, maker wallet) and a useful edge case (empty list rather than 404). It doesn't mention pagination or that 'every' listing may span multiple pages via limit/cursor, which is a minor gap given the pagination parameters in the schema.

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 sentences with zero fluff. The core action and scope are in the first sentence, and the second adds essential return details and an edge case. Every sentence earns its place.

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?

The description explains what is returned and the empty-list behavior, which is valuable given there is no output schema. It lacks an explicit mention of pagination behavior even though limit/cursor exist, and does not note that chain values come from /opensea/chains (which the schema does mention). Overall, sufficiently complete for an agent to call it correctly.

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 fully documents all six parameters. The description adds no parameter-level detail beyond what the schema provides, meeting the baseline of 3.

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 standing listings for an OpenSea NFT.' It clearly distinguishes from sibling tools like opensea_item_offers (offers) and opensea_item_activity (activity) by specifying sell orders, and names the returned fields. An agent can tell exactly what this tool does.

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: it is the tool for standing sell orders/listings for a single NFT, not offers, owners, or activity. It doesn't explicitly name alternatives or state when not to use it, but the 'standing listings' vs. other identifiable OpenSea item tools is reasonably clear.

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