Skip to main content
Glama

Opensea Get Collection

opensea_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/.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection_slug": "cryptopunks"
    },
    "name": "opensea_get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collection_slugYesOpenSea collection slug (URL suffix)

Output Schema

NameRequiredDescriptionDefault
feesYesCollection fees
nameYesCollection name
nsfwYesWhether collection is marked NSFW
slugYesCollection slug identifier
wikiYesWiki URL
imageYesCollection image URL
ownerYesCollection owner address
bannerYesCollection banner image URL
discordYesDiscord server URL
twitterYesTwitter username
websiteYesProject website URL
categoryYesCollection category
disabledYesWhether collection is disabled
telegramYesTelegram group URL
contractsYesSmart contracts associated with collection
instagramYesInstagram username
descriptionYesCollection description
opensea_urlYesOpenSea collection page URL
total_supplyYesTotal token supply
safelist_statusYesOpenSea safelist verification status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and idempotency profile is covered. The description adds the set of metadata fields returned, but says nothing about rate limits, caching, or what happens for an unknown slug, and the output schema already carries return details.

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?

Three short sentences with the core action front-loaded, followed by return fields and then input sourcing. Nothing is redundant or padded.

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 single-parameter read tool with rich annotations and an output schema, this is close to complete: purpose, returned data, and input sourcing are all covered. The only omission is failure behavior for a non-existent slug, which is minor given the structured fields.

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 the schema already labels the parameter as an OpenSea collection slug (URL suffix), so the baseline is 3. The description goes slightly beyond by giving the concrete URL pattern opensea.io/collection/<slug> as a way to source valid slug values.

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?

States a specific verb and resource ('Fetch a collection by OpenSea slug') and enumerates the fields returned, which lets an agent tell it apart from get_collection_stats and list_collection_nfts. It stops short of naming those siblings explicitly, so it is clear but not fully differentiated.

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?

Usage is implied by the slug-based lookup and the hint 'Find slugs at opensea.io/collection/<slug>', which helps an agent supply the right input. There is no explicit when-to-use/when-not guidance or comparison with alternatives such as get_collection_stats.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.