Opensea

List Owned Nfts

list_owned_nfts

Read-onlyIdempotent

NFTs owned by an address on a specific chain. Paginated.

Input Schema

TableJSON Schema

Name	Required	Description
`next`	No	Pagination cursor
`chain`	Yes	Chain slug
`limit`	No	1-200 (default 50)
`address`	Yes	Owner wallet address
`collection_slug`	No	Restrict to a single collection (optional)

Output Schema

TableJSON Schema

Name	Required	Description
`next`	Yes	Pagination cursor for next page
`nfts`	Yes	NFTs owned by address
`chain`	Yes	Blockchain chain queried
`count`	Yes	Number of NFTs in this page
`owner`	Yes	Owner wallet address

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "address": "0x1234567890abcdef1234567890abcdef12345678",
+    "chain": "ethereum",
+    "limit": 50
+  },
+  {
+    "address": "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd",
+    "chain": "polygon",
+    "collection_slug": "boredapeyachtclub"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "chain": {
+      "description": "Blockchain chain 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 owned by address",
+      "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"
+    },
+    "owner": {
+      "description": "Owner wallet address",
+      "type": "string"
+    }
+  },
+  "required": [
+    "chain",
+    "owner",
+    "count",
+    "next",
+    "nfts"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds 'Paginated' which is useful context beyond annotations, but does not detail rate limits, error behavior, or what happens with invalid addresses.

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, no fluff, front-loaded with the core action. Every word 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?

Given an output schema exists (not shown but noted as true), the description does not need to explain return values. It covers the essential context: ownership, chain, address, and pagination. Minor gaps like handling invalid addresses are acceptable for a list endpoint.

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 coverage is 100% with descriptions for each parameter. The description adds no new parameter meaning beyond the schema, except implicitly linking 'next' to pagination. The baseline of 3 is appropriate.

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?

The description clearly states it lists NFTs owned by an address on a specific chain, and mentions pagination. This distinguishes it from siblings like get_nft (single NFT) and list_collection_nfts (NFTs in a collection).

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?

The description implicitly suggests when to use (to list owned NFTs by address/chain) but does not explicitly state when not to use or mention alternatives. It is clear enough for a simple list tool.

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.