Opensea

Get Nft

get_nft

Read-onlyIdempotent

Single NFT by chain + contract address + token ID.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes	Chain slug (ethereum, polygon, base, arbitrum, optimism, avalanche, klaytn, bsc, solana, etc.)
`token_id`	Yes	Token ID (numeric string for ERC-721/1155)
`contract_address`	Yes	Contract address (0x... for EVM)

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	NFT name
`nsfw`	Yes	Whether NFT is marked NSFW
`image`	Yes	Display image URL
`owners`	Yes	Current owners (for ERC1155 multiple owners possible)
`traits`	Yes	NFT traits/attributes
`contract`	Yes	Contract address
`disabled`	Yes	Whether NFT is disabled
`standard`	Yes	Token standard (ERC721, ERC1155)
`animation`	Yes	Animation/video URL
`collection`	Yes	Collection slug
`identifier`	Yes	Token ID
`updated_at`	Yes	Last update timestamp
`description`	Yes	NFT description
`opensea_url`	Yes	OpenSea item page URL
`rarity_rank`	Yes	Rarity rank in collection
`metadata_url`	Yes	Metadata URL
`rarity_score`	Yes	Rarity score

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "chain": "ethereum",
+    "contract_address": "0xbc4ca0eda7647a8ab7c2061c2e2ad7d5d0d6c10a",
+    "token_id": "1"
+  },
+  {
+    "chain": "solana",
+    "contract_address": "EPjFWaLb3hyJCKESKAul7f2z6VJiGipHvd9pRnqYQts",
+    "token_id": "42"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+      ]
+    }
+  },
+  "required": [
+    "identifier",
+    "collection",
+    "contract",
+    "standard",
+    "name",
+    "description",
+    "image",
+    "animation",
+    "metadata_url",
+    "opensea_url",
+    "updated_at",
+    "disabled",
+    "nsfw",
+    "traits",
+    "owners",
+    "rarity_rank",
+    "rarity_score"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint as false. The description adds minimal behavioral context beyond stating the output is a single NFT. It neither contradicts nor enriches the annotations significantly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no redundant words, achieving conciseness. It is front-loaded with the core action. However, it could be slightly more structured by hinting at the output shape.

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 tool with three parameters and an existing output schema, the description provides sufficient context. It does not explain return values, but the output schema fills that gap. The tool's simplicity and annotations make it adequately complete.

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 each parameter already described. The tool description does not add new meaning or constraints beyond mentioning the three parameters, so the baseline score 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 the tool retrieves a single NFT by three identifiers: chain, contract address, and token ID. This verb+resource combination is specific and distinguishes it from siblings like get_collection or list_collection_nfts.

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?

No explicit guidance on when to use this tool versus alternatives. While the context implies it is for fetching a specific NFT, the description does not provide when-not-to-use or mention sibling functions, leaving the agent to infer from names.

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.