Opensea

Get Collection

get_collection

Read-onlyIdempotent

Fetch a collection by OpenSea slug. Returns name, description, contracts, social links, fees, image, banner. Find slugs at opensea.io/collection/.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`collection_slug`	Yes	OpenSea collection slug (URL suffix)

Output Schema

TableJSON Schema

Name	Required	Description
`fees`	Yes	Collection fees
`name`	Yes	Collection name
`nsfw`	Yes	Whether collection is marked NSFW
`slug`	Yes	Collection slug identifier
`wiki`	Yes	Wiki URL
`image`	Yes	Collection image URL
`owner`	Yes	Collection owner address
`banner`	Yes	Collection banner image URL
`discord`	Yes	Discord server URL
`twitter`	Yes	Twitter username
`website`	Yes	Project website URL
`category`	Yes	Collection category
`disabled`	Yes	Whether collection is disabled
`telegram`	Yes	Telegram group URL
`contracts`	Yes	Smart contracts associated with collection
`instagram`	Yes	Instagram username
`description`	Yes	Collection description
`opensea_url`	Yes	OpenSea collection page URL
`total_supply`	Yes	Total token supply
`safelist_status`	Yes	OpenSea safelist verification status

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "collection_slug": "cryptopunks"
+  },
+  {
+    "collection_slug": "boredapeyachtclub"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "banner": {
+      "description": "Collection banner image URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "category": {
+      "description": "Collection category",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "contracts": {
+      "description": "Smart contracts associated with collection",
+      "items": {
+        "properties": {
+          "address": {
+            "description": "Contract address",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "chain": {
+            "description": "Blockchain chain name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "description": {
+      "description": "Collection description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "disabled": {
+      "description": "Whether collection is disabled",
+      "type": "boolean"
+    },
+    "discord": {
+      "description": "Discord server URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fees": {
+      "description": "Collection fees",
+      "items": {
+        "properties": {
+          "pct": {
+            "description": "Fee percentage",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "recipient": {
+            "description": "Fee recipient address",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "required": {
+            "description": "Whether fee is required",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "image": {
+      "description": "Collection image URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "instagram": {
+      "description": "Instagram username",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Collection name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nsfw": {
+      "description": "Whether collection is marked NSFW",
+      "type": "boolean"
+    },
+    "opensea_url": {
+      "description": "OpenSea collection page URL",
+      "type": "string"
+    },
+    "owner": {
+      "description": "Collection owner address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "safelist_status": {
+      "description": "OpenSea safelist verification status",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slug": {
+      "description": "Collection slug identifier",
+      "type": "string"
+    },
+    "telegram": {
+      "description": "Telegram group URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total_supply": {
+      "description": "Total token supply",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "twitter": {
+      "description": "Twitter username",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "website": {
+      "description": "Project website URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "wiki": {
+      "description": "Wiki URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "slug",
+    "name",
+    "description",
+    "image",
+    "banner",
+    "owner",
+    "safelist_status",
+    "category",
+    "disabled",
+    "nsfw",
+    "opensea_url",
+    "website",
+    "wiki",
+    "discord",
+    "telegram",
+    "twitter",
+    "instagram",
+    "contracts",
+    "total_supply",
+    "fees"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive hints. The description adds value by detailing the exact return fields (name, description, contracts, etc.) and how to obtain the slug, providing behavioral context beyond annotations.

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 two concise sentences with no filler. It front-loads the purpose and quickly provides additional context for parameter usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (single parameter, output schema exists, rich annotations), the description covers purpose, return fields, and slug sourcing. It is complete and leaves no ambiguity for an AI agent.

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% and already describes the parameter. The description adds practical guidance ('Find slugs at opensea.io/collection/<slug>'), which provides helpful context beyond the schema's description.

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 uses a specific verb ('Fetch') and resource ('collection by OpenSea slug'), clearly distinguishing it from siblings like get_collection_stats or list_collection_nfts. It also lists the returned fields.

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 tells when to use this tool (to get collection metadata by slug) and provides guidance on finding slugs. However, it does not explicitly differentiate from alternatives like get_collection_stats, though the distinction is clear from context.

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.