Opensea

List Collection Nfts

list_collection_nfts

Read-onlyIdempotent

List NFTs inside a collection (paginated). Returns identifier, name, image, traits, owner, last sale.

Input Schema

TableJSON Schema

Name	Required	Description
`next`	No	Pagination cursor from prior response
`limit`	No	1-200 (default 50)
`collection_slug`	Yes	OpenSea collection slug

Output Schema

TableJSON Schema

Name	Required	Description
`next`	Yes	Pagination cursor for next page
`nfts`	Yes	NFTs in collection
`count`	Yes	Number of NFTs in this page
`collection_slug`	Yes	Collection slug queried

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "collection_slug": "boredapeyachtclub",
+    "limit": 50
+  },
+  {
+    "collection_slug": "cryptopunks",
+    "limit": 100,
+    "next": "eyJvZmZzZXQiOiAxMDB9"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "collection_slug": {
+      "description": "Collection slug queried",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of NFTs in this page",
+      "type": "number"
+    },
+    "next": {
+      "description": "Pagination cursor for next page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nfts": {
+      "description": "NFTs in collection",
+      "items": {
+        "properties": {
+          "animation": {
+            "description": "Animation/video URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "collection": {
+            "description": "Collection slug",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "contract": {
+            "description": "Contract address",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "NFT description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "disabled": {
+            "description": "Whether NFT is disabled",
+            "type": "boolean"
+          },
+          "identifier": {
+            "description": "Token ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "image": {
+            "description": "Display image URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "metadata_url": {
+            "description": "Metadata URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "NFT name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "nsfw": {
+            "description": "Whether NFT is marked NSFW",
+            "type": "boolean"
+          },
+          "opensea_url": {
+            "description": "OpenSea item page URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "owners": {
+            "description": "Current owners (for ERC1155 multiple owners possible)",
+            "items": {
+              "properties": {
+                "address": {
+                  "description": "Owner address",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "quantity": {
+                  "description": "Quantity owned",
+                  "type": "number"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "rarity_rank": {
+            "description": "Rarity rank in collection",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "rarity_score": {
+            "description": "Rarity score",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "standard": {
+            "description": "Token standard (ERC721, ERC1155)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "traits": {
+            "description": "NFT traits/attributes",
+            "items": {
+              "properties": {
+                "display_type": {
+                  "description": "Display type hint",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "type": {
+                  "description": "Trait name",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "value": {
+                  "description": "Trait value",
+                  "type": [
+                    "string",
+                    "number",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "updated_at": {
+            "description": "Last update timestamp",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "collection_slug",
+    "count",
+    "next",
+    "nfts"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behaviors. The description adds that the tool is paginated and returns specific fields, which is useful but does not explain pagination mechanics or other behavioral traits beyond what annotations provide.

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 a single sentence with 13 words, efficiently conveying purpose and output without redundancy or unnecessary detail.

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 tool's simplicity, strong annotations, and presence of an output schema, the description is mostly complete. It lacks a brief note on pagination flow (e.g., how to use the 'next' cursor), but overall covers the essential information.

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 parameters. The description only adds 'paginated' context, which is already implied by the 'next' parameter. No additional semantic value beyond the schema.

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 it lists NFTs inside a collection with pagination and specifies return fields. It implicitly differentiates from siblings like 'list_owned_nfts' by scoping to a collection, but does not explicitly distinguish or name alternatives.

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 use when listing NFTs in a collection but provides no explicit guidance on when to use versus alternatives like 'get_nft' or 'list_owned_nfts'. No exclusions or prerequisites are mentioned.

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

All Opensea tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.